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

[Mike Jackson]

You need to look at the following CMake modules:

# -- Run the BundleUtilities cmake code
include(BundleUtilities)

Then you need to include a call to the right macros within that module
to get cmake to package up your app into a standalone bundle.

I have an example that uses Qt at the following location:

http://www.bluequartz.net/software/files/QtTest.tar.gz

It should be enough to get you going. If you have questions just ask the list.
--
Mike Jackson
www.bluequartz.net

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
>