Re: [CMake] Using CPack with OSX 10.9
Thanks Norman, Spot on – definitely feeling like we’re running against the grain here. Will check out the Cmake package as that sounds like a good example. Cheers, Lachlan Hetherton Software Engineer (Visualisation) ☎ +613-9545-8041 From: "Williams, Norman K" mailto:norman-k-willi...@uiowa.edu>> Date: Tue, 29 Jul 2014 17:18:10 + To: Lachlan Hetherton mailto:lachlan.hether...@csiro.au>>, "cmake@cmake.org<mailto:cmake@cmake.org>" mailto:cmake@cmake.org>> Subject: Re: [CMake] Using CPack with OSX 10.9 I would look at how CMake itself is packaged for release. The ‘one executable per App bundle’ is Apple-centric thinking that luckily is not enforced. That isn’t how CMakes (or the OS X Emacs, e.g.) works. You can have whatever you want in an app bundle. It does means that after install, users need to add the directory inside the bundle to their PATH environment variable, if the extra programs are meant to be command line executables. You’d want whatever GUI program that is your main program to be the executable run when you open the app bundle. The problem is that what you’re trying to do doesn’t map neatly onto the Apple world, so you have to choose the least worst workaround. For that matter, using a compressed tar instead of an App Bundle would work too. From: "lachlan.hether...@csiro.au<mailto:lachlan.hether...@csiro.au>" mailto:lachlan.hether...@csiro.au>> Date: Monday, July 28, 2014 at 8:06 PM To: CMake Users mailto:cmake@cmake.org>> Subject: [CMake] Using CPack with OSX 10.9 Hi there, We’re looking to update our CMake packaging scripts so that we can deploy to OSX 10.9 Mavericks. For previous OSX releases, we have used the PackageMaker generator with CPack to create .pkg files inside .dmg files. I believe PackageMaker has now disappeared (I can’t run the old version on my current machine and there doesn’t seem to be a new version available anywhere), so I would like to ask you all: what is the preferred generator for deploying to OSX 10.9? I’m currently looking into the OSX Bundle generator, however, our application ships with multiple executables and a number of dependent libraries and frameworks, so I’m not quite sure whether this is the right way to go. From what I’ve read, OSX application bundles are supposed to have a single executable only – how would I go about deploying an application that has multiple component applications? If we use the bundle generator, our application is going to look like this (I think), which seems strange: OurApplication.app/ Contents/ Info.plist MacOS/ executable1 Frameworks/ QtCore.framework QtGui.framework … Resources/ bin/ executable1 executable2 … lib/ non-framework dependencies Thanks for your help, Lachlan Hetherton Software Engineer (Visualisation) ☎ +613-9545-8041 Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Using CPack with OSX 10.9
Hi Sean, The confusion I am having about deploying in a .app is: 1. We currently ship with >1 executable. .app bundles are only supposed to have 1 executable (I think) 2. Our application is designed to allow others to build plug-ins for it. Not sure how this works if we deploy as a .app. Maybe we should be deploying as an umbrella framework or something similar? Thanks, Lachlan Hetherton Software Engineer (Visualisation) ☎ +613-9545-8041 On 7/30/14, 1:07 AM, "Sean McBride" wrote: >On Tue, 29 Jul 2014 01:06:26 +, lachlan.hether...@csiro.au said: > >>I’m currently looking into the OSX Bundle generator, however, our >>application ships with multiple executables and a number of dependent >>libraries and frameworks, so I’m not quite sure whether this is the >>right way to go. From what I’ve read, OSX application bundles are >>supposed to have a single executable only – how would I go about >>deploying an application that has multiple component applications? If we >>use the bundle generator, our application is going to look like this (I >>think), which seems strange: >> >>OurApplication.app/ >>Contents/ >>Info.plist >>MacOS/ >>executable1 >>Frameworks/ >>QtCore.framework >>QtGui.framework >>… >>Resources/ >>bin/ >>executable1 >>executable2 >>… >>lib/ >>non-framework dependencies > >What's strange about it? It's generally strongly preferred for an OS X >application to be self-contained in a .app. There are times when it's >not possible, which is maybe your case? What do you need to install >where? > >Cheers, > >-- > >Sean McBride, B. Eng s...@rogue-research.com >Rogue Researchwww.rogue-research.com >Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Using CPack with OSX 10.9
I would look at how CMake itself is packaged for release. The ‘one executable per App bundle’ is Apple-centric thinking that luckily is not enforced. That isn’t how CMakes (or the OS X Emacs, e.g.) works. You can have whatever you want in an app bundle. It does means that after install, users need to add the directory inside the bundle to their PATH environment variable, if the extra programs are meant to be command line executables. You’d want whatever GUI program that is your main program to be the executable run when you open the app bundle. The problem is that what you’re trying to do doesn’t map neatly onto the Apple world, so you have to choose the least worst workaround. For that matter, using a compressed tar instead of an App Bundle would work too. From: "lachlan.hether...@csiro.au<mailto:lachlan.hether...@csiro.au>" mailto:lachlan.hether...@csiro.au>> Date: Monday, July 28, 2014 at 8:06 PM To: CMake Users mailto:cmake@cmake.org>> Subject: [CMake] Using CPack with OSX 10.9 Hi there, We’re looking to update our CMake packaging scripts so that we can deploy to OSX 10.9 Mavericks. For previous OSX releases, we have used the PackageMaker generator with CPack to create .pkg files inside .dmg files. I believe PackageMaker has now disappeared (I can’t run the old version on my current machine and there doesn’t seem to be a new version available anywhere), so I would like to ask you all: what is the preferred generator for deploying to OSX 10.9? I’m currently looking into the OSX Bundle generator, however, our application ships with multiple executables and a number of dependent libraries and frameworks, so I’m not quite sure whether this is the right way to go. From what I’ve read, OSX application bundles are supposed to have a single executable only – how would I go about deploying an application that has multiple component applications? If we use the bundle generator, our application is going to look like this (I think), which seems strange: OurApplication.app/ Contents/ Info.plist MacOS/ executable1 Frameworks/ QtCore.framework QtGui.framework … Resources/ bin/ executable1 executable2 … lib/ non-framework dependencies Thanks for your help, Lachlan Hetherton Software Engineer (Visualisation) ☎ +613-9545-8041 Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Using CPack with OSX 10.9
On Tue, 29 Jul 2014 01:06:26 +, lachlan.hether...@csiro.au said: >I’m currently looking into the OSX Bundle generator, however, our >application ships with multiple executables and a number of dependent >libraries and frameworks, so I’m not quite sure whether this is the >right way to go. From what I’ve read, OSX application bundles are >supposed to have a single executable only – how would I go about >deploying an application that has multiple component applications? If we >use the bundle generator, our application is going to look like this (I >think), which seems strange: > >OurApplication.app/ >Contents/ >Info.plist >MacOS/ >executable1 >Frameworks/ >QtCore.framework >QtGui.framework >… >Resources/ >bin/ >executable1 >executable2 >… >lib/ >non-framework dependencies What's strange about it? It's generally strongly preferred for an OS X application to be self-contained in a .app. There are times when it's not possible, which is maybe your case? What do you need to install where? Cheers, -- Sean McBride, B. Eng s...@rogue-research.com Rogue Researchwww.rogue-research.com Mac Software Developer Montréal, Québec, Canada -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Using CPack with OSX 10.9
As a further FYI, I have tried installing that version of PackageMaker and it simply crashes on load, so I’m not sure whether this is even an option any more. Regards, Lachlan Hetherton Software Engineer (Visualisation) ☎ +613-9545-8041 On 7/29/14, 11:31 AM, "Mihai Moldovan" wrote: >On 29.07.2014 03:06 am, lachlan.hether...@csiro.au wrote: >> I believe PackageMaker has now disappeared (I can’t run the old version >>on my >> current machine and there doesn’t seem to be a new version available >>anywhere) > >A Mavericks-compatible version of PackageMaker is available on >https://developer.apple.com/downloads/, search for "Auxiliary Tools For >Xcode - >Late July 2012". > >While this does not help you in the long run (PackageMaker is deprecated >and has >already been removed from the most current AuxTools package as you have >noticed), it may enable you to keep working with the current setup you >have >right now for some more time. > > > >Mihai > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Using CPack with OSX 10.9
On 29.07.2014 03:06 am, lachlan.hether...@csiro.au wrote: > I believe PackageMaker has now disappeared (I can’t run the old version on my > current machine and there doesn’t seem to be a new version available anywhere) A Mavericks-compatible version of PackageMaker is available on https://developer.apple.com/downloads/, search for "Auxiliary Tools For Xcode - Late July 2012". While this does not help you in the long run (PackageMaker is deprecated and has already been removed from the most current AuxTools package as you have noticed), it may enable you to keep working with the current setup you have right now for some more time. Mihai smime.p7s Description: S/MIME Cryptographic Signature -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
Re: [CMake] Using CPack with OSX 10.9
Thanks Mihai, That’s good to know. Having said that, I’m now knee deep in this stuff so if anyone has any recommendations on how to proceed going forward (e.g. with app bundles), that would be great. Regards, Lachlan Hetherton Software Engineer (Visualisation) ☎ +613-9545-8041 On 7/29/14, 11:31 AM, "Mihai Moldovan" wrote: >On 29.07.2014 03:06 am, lachlan.hether...@csiro.au wrote: >> I believe PackageMaker has now disappeared (I can’t run the old version >>on my >> current machine and there doesn’t seem to be a new version available >>anywhere) > >A Mavericks-compatible version of PackageMaker is available on >https://developer.apple.com/downloads/, search for "Auxiliary Tools For >Xcode - >Late July 2012". > >While this does not help you in the long run (PackageMaker is deprecated >and has >already been removed from the most current AuxTools package as you have >noticed), it may enable you to keep working with the current setup you >have >right now for some more time. > > > >Mihai > -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Using CPack with OSX 10.9
Hi there, We’re looking to update our CMake packaging scripts so that we can deploy to OSX 10.9 Mavericks. For previous OSX releases, we have used the PackageMaker generator with CPack to create .pkg files inside .dmg files. I believe PackageMaker has now disappeared (I can’t run the old version on my current machine and there doesn’t seem to be a new version available anywhere), so I would like to ask you all: what is the preferred generator for deploying to OSX 10.9? I’m currently looking into the OSX Bundle generator, however, our application ships with multiple executables and a number of dependent libraries and frameworks, so I’m not quite sure whether this is the right way to go. From what I’ve read, OSX application bundles are supposed to have a single executable only – how would I go about deploying an application that has multiple component applications? If we use the bundle generator, our application is going to look like this (I think), which seems strange: OurApplication.app/ Contents/ Info.plist MacOS/ executable1 Frameworks/ QtCore.framework QtGui.framework … Resources/ bin/ executable1 executable2 … lib/ non-framework dependencies Thanks for your help, Lachlan Hetherton Software Engineer (Visualisation) ☎ +613-9545-8041 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
