compile ogre-next from source along side ogre.

OGRECave / ogre-next

aka ogre v2 - scene-oriented, flexible 3D C++ engine

https://ogrecave.github.io/ogre-next/api/latest

Other

1.08k stars 233 forks source link

compile ogre-next from source along side ogre. #419

Closed talregev closed 1 year ago

talregev commented 1 year ago

As a vcpkg user, I would like to compile ogre-next along side ogre. The problem is, that when I compile it from source it have the same name as original ogre lib. Can you differentiate this library lib binary file name from ogre? Maybe as you ship it as ogre-next? Similar to your repo name.

darksylinc commented 1 year ago

Hi!

See #259

OgreNext 2.3 added the OGRE_USE_NEW_PROJECT_NAME CMake option to address this issue.

The roadmap is as follows:

OgreNext 3.0 OGRE_USE_NEW_PROJECT_NAME is off by default.
OgreNext 4.0 OGRE_USE_NEW_PROJECT_NAME is on by default.
OgreNext 5.0 OGRE_USE_NEW_PROJECT_NAME is marked as deprecated.
OgreNext 6.0 will not ship with OGRE_USE_NEW_PROJECT_NAME.

talregev commented 1 year ago

On version 2.3.1 is still not there: https://github.com/OGRECave/ogre-next/blob/v2.3.1/CMakeLists.txt

Can you release 2.3.2?

talregev commented 1 year ago

Until you don't release a new version that contain this fix, the issue still remain. Please open the issue.

darksylinc commented 1 year ago

Sounds fair.

darksylinc commented 1 year ago

2.3.2 has been released. Closing.

Tomorrow I'll be updating the main website. We'll soon be making a 3.0 release too; if you have naming candidates, they're welcome.

Cheers