-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas Sharpless wrote: > What is the best way to ensure that release and debug targets get the > appropriate link libraries? Does cmake have a policy for this?
TARGET_LINK_LIBRARIES allows you to specify an optional "debug" or "optimized" argument which you can use to control which form of a library you're linking a target against (a debug or release). There is no CMake policy I'm aware of on this. It's pretty much up to the users. > Is there any support for checking that the set of runtime libraries to > be used is consistent? Specifically, can I scan the linker directives > in prebuilt static libraries? I'm not sure what you're asking here. Prebuilt static libraries don't store linker directives. CMake allows you to manipulate the linking parameters using the LINK_FLAGS property of SET_TARGET_PROPERTIES(). - -- Philip Lowman -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHLeEte0tOktX6RKkRAuyWAJ9Fx4A4bYcB7Yb0BPQaeb3hs5yIuwCeONCl r+UgZrg9D7fQnDLsackTzpw= =CRz1 -----END PGP SIGNATURE----- _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
