[CMake] CPack MacOSX support

2007-10-11 Thread Félix C. Morency
Hi, 1. Is there any way to include 3rd party libraries in a generated bundle (.app) with CMake/CPack (.dmg) ? Currently, the 3rd party are out of the bundle and this is quite ungood since the bundle architecture provides resources support. Anyone ever done it before ? 2. The PackageMaker (.dmg)

Re: [CMake] CPack MacOSX support

2007-10-11 Thread David Cole
On 10/11/07, Félix C. Morency [EMAIL PROTECTED] wrote: 1. Is there any way to include 3rd party libraries in a generated bundle (.app) with CMake/CPack (.dmg) ? Currently, the 3rd party are out of the bundle and this is quite ungood since the bundle architecture provides resources support.

Re: [CMake] CPack MacOSX support

2007-10-11 Thread Mike Jackson
along these same lines, how is cmake handling the issue with paths in OS X libraries such as @executable_path/../Frameworks ? Simply copying the library inside the App bundle will not work most of the time. Is there any upcoming support to allow the setting of the rpath in generated

Re: [CMake] CPack MacOSX support

2007-10-11 Thread Félix C. Morency
For the mailing list: David, Thank you for you fast answer. 1. Yes, I actually want to copy some libOne.dylib directly into the bundle so all the required library can be into the .app bundle (at the same place the executable is) and not outside. Another way to say it would be that I want

Re: [CMake] CPack MacOSX support

2007-10-11 Thread David Cole
If the library is built by CMake, you can use the INSTALL_NAME_DIR property to achieve @executable_path or @loader_path relative references. This example comes from CMake/Tests/BundleTest/CMakeLists.txt: SET_TARGET_PROPERTIES(BundleTestLib PROPERTIES INSTALL_NAME_DIR