Closed talregev closed 1 year ago
It coming from here: https://github.com/OGRECave/ogre-next/blob/master/CMake/Templates/OGREStatic.pc.in Is it not update by purpose? I can make a patch on vcpkg side.
I think also here: https://github.com/OGRECave/ogre-next/blob/491d37df15c048cd4757cd57d3091cec7c255fc5/RenderSystems/Direct3D11/CMakeLists.txt#L64
install(FILES ${HEADER_FILES} DESTINATION include/OGRE/RenderSystems/Direct3D11) ->
install(FILES ${HEADER_FILES} DESTINATION include/${OGRE_NEXT_PREFIX}/RenderSystems/Direct3D11)
Thank you!
Thank you for reporting it!
I'm planning on making a new 2.3 release to address this issue.
System Information
Detailled description
I compile ogre-next 2.3.2 on vcpkg with the flag:
-DOGRE_USE_NEW_PROJECT_NAME=ON
to have the new name of ogre-next. It compile successful with the new name on the libs. but the pc file didn't not update to the new name:it should change the name the include folder and the linkage flags:
Ogre.log
Callstack
Not relevant. not in run time.