[CMake] OS X Bundle building -- adding external DYLIB files?

[kent williams]

I was able to use this example to successfully build a standalone
application. Many thanks!

One thing: I had to set EXECUTABLE_OUTPUT_PATH in my CMakeLists.txt
file -- otherwise when it built the install scripts that variable was
empty and it wasn't finding my application at all.

And with CMake 2.6.3 I get this warning:

CMake Warning (dev) at cmake_install.cmake:31 (INCLUDE):
  Policy CMP0011 is not set: Included scripts do automatic cmake_policy PUSH
  and POP.  Run "cmake --help-policy CMP0011" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  The included script

    /scratch/kent/paulstretch/paulstretch-build/paulstretch_OSX_MakeStandAloneBundle.cmake

  affects policy settings.  CMake is implying the NO_POLICY_SCOPE option for
  compatibility, so the effects are applied to the including context.
This warning is for project developers.  Use -Wno-dev to suppress it.


On Tue, Apr 28, 2009 at 2:52 PM, Mike Jackson
<mike.jackson at bluequartz.net> wrote:
> There is also this wiki entry that might help.
>
> http://www.cmake.org/Wiki/BundleUtilitiesExample
>
> Mike Jackson
>
> On Tue, Apr 28, 2009 at 2:21 PM, kent williams
> <nkwmailinglists at gmail.com> wrote:
>> I just wrote a CMakeLists.txt file for a program that depends on a
>> bunch of libraries that I had to build before building the
>> application.
>>
>> I want to generate a deliverable OS X bundle, but I'm neither an OS X
>> development expert nor a CMAKE OS X bundle expert.
>>
>> Simply put, I want to do the absolute minimum in order to package the
>> DYLIB files in the bundle and have the application know to use those
>> DYLIB files.
>>
>> How does one do this?
>>
>> Right now, the application that gets built seems to refer to these
>> DYLIB files by their absolute path where I built them.  This makes
>> giving the program to anyone who doesn't have those libraries at
>> exactly the same absolute path impossible.
>>
>> I have read the CMake documentation, and done some searching around
>> with Google, without much enlightenment.  If you think I need to just
>> RTFM -- point me to TFM please ;-)
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>>
>