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" <[email protected]> wrote:

>On Tue, 29 Jul 2014 01:06:26 +0000, [email protected] 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                 [email protected]
>Rogue Research                        www.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

Reply via email to