And just to follow up with my own answer I have a file that gets "configured"
during CMake time with the following code in it:
include(BundleUtilities)
fixup_bundle("@CMAKE_INSTALL_PREFIX@/@tar...@.app" "@COMPLETE_PLUGIN_LIST@"
"@PLUGIN_SEARCH_DIRS@")
Which hard codes the complete installation path. What I did not realize was
that CPack is actually setting the CMAKE_INSTALL_PREFIX and then running the
installation cmake code. So replacing the above with:
include(BundleUtilities)
fixup_bundle("${CMAKE_INSTALL_PREFIX}/@tar...@.app" "@COMPLETE_PLUGIN_LIST@"
"@PLUGIN_SEARCH_DIRS@")
Allows the CPack code to run properly and give me a properly generated OS X App
bundle.
Sorry for the noise.
___________________________________________________________
Mike Jackson www.bluequartz.net
On Aug 19, 2010, at 7:51 PM, Michael Jackson wrote:
> I have a CMake based project that produces an OS X App bundle with libraries,
> Frameworks, and plugins. If I do a "make install" then the app bundle is
> created just fine. But if I do "make package" then I get the "shell" of the
> app bundle but none of the required libraries are include. Kinda like "make
> install" should be run first before "make package".
> I know I am missing something simple with this but I am just not seeing it.
> Any help would be appreciated.
>
> Thanks
> ___________________________________________________________
> Mike Jackson www.bluequartz.net
> Principal Software Engineer mike.jack...@bluequartz.net
> BlueQuartz Software Dayton, Ohio
>
>
>
_______________________________________________
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
