On Friday 16 January 2009 16:01:55 Clinton Stimpson wrote: > I've already done this, so when I do a "make install," I get all my > bundles with install names fixed, with prerequisites, etc... It works > fine with CPack/PackageMaker generator which also makes the top level > folder to contain all the apps, so it installs nicely except for a root > ownership problem. But it doesn't work with the CPack/Bundle generator > since it tries to re-bundle the bundles that I've already got. I guess > I could take the last two easy steps, make the /Applications link and > the dmg myself. Seems to me those two steps is all the cpack bundle > generator needs to be doing, and the rest of the work of creating the > bundle be done by the "make install" step. No? Maybe a new cpack/dmg > generator that just takes what make install gives, optionally adds a > softlink such as /Applications, and makes a dmg? There are three methods of making Bundles in CMake, you need to make sure you are only using one at a time. I'm guess you've set the MACOSX_BUNDLE parameter on your executable to cause this behaviour.
The Bundle generator was written from outside of CMake and I agree it could do with a bit of a consistency cleanup. You can, however, get it working fine with a bit of work, my employers OSX packages use the CMake Bundle generator (http://www.mendeley.com) > I was impressed that what I had done to make a nice NSIS installer also > worked just fine with PackageMaker. I like that consistency. I didn't > see that with the bundle generator. Yeh, as I say, it needs a bit of work and to do a few more checks to stop you shooting yourself in the foot. -- Cheers, Mike Arthur http://mikearthur.co.uk/ _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
