cmake INSTALL_LIBS usage?

[ejtttje]

I'm not sure I understand the rationale of this patch:
http://code.google.com/p/bullet/source/ ... 064&r=1984
which added the INSTALL_LIBS option.

As far as I know, nothing is installed unless you do a 'make install' (or similar depending on environment). So I'm not sure what the point of this is other than to disable the ability to do 'make install', which if you didn't want, you can just not do.

In particular for building a OS X framework, because of this now we need to specify -DINSTALL_LIBS=ON as well as -DBUILD_SHARED_LIBS=ON -DFRAMEWORK=ON... getting kind of verbose. Is there an easy way to tell cmake if FRAMEWORK is set, then BUILD_SHARED_LIBS and INSTALL_LIBS should both be turned on as well?

(FYI, for frameworks there is a notion of the install path being set to /Library/Frameworks if "installed", or @executable_path/.. if "embedded" in an application. But I think this is best addressed by the native CMAKE_INSTALL_NAME_DIR as opposed to adapting INSTALL_LIBS...)

Thanks -Ethan

[Erwin Coumans]

As far as I know, nothing is installed unless you do a 'make install' (or similar depending on environment).
Is there an easy way to tell cmake if FRAMEWORK is set, then BUILD_SHARED_LIBS and INSTALL_LIBS should both be turned on as well?

Good idea, we can add such option when FRAMEWORK is set. We just don't want to see a 'INSTALL' project in the generated Visual Studio or OSX Xcode projectfiles by default.

Thanks,
Erwin