kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #14897
OSX Build changes.
Hi Bernhard,
I looked around through the application bundle you posted and had some questions about the proposed layout. It seems there is some arbitrary placement of files in the bundle. I know it ultimately doesn’t matter to most users as long as it runs and behaves properly but it doesn’t really follow the usual guidelines for layout.
Is there any chance that the dylibs could not be dumped in the MacOS directory? They really don’t belong there, as is the case for most everything in there. I think these should be in a Frameworks directory at the very least. Also, and this is just a point of curiosity, but why is libX11 included in these libraries? What requires that to run?
Same for the command line binaries, they are things that are not required for the application to run so belong out in a support directory of some kind.
I’m not familiar with the kiface files, but they appear to be loadable bundles, which also don’t belong there. Probably belong in a PlugIns directory
It looks like the remainder of the applications are in there as well, albeit not integrated into application bundles themselves. Not really sure how those should be integrated, but putting their pieces in the MacOS directory doesn’t seem ideal. Any chance these applications could just be consumed whole in an Applications directory inside the main app? Apple does this for some of their own applications. It doesn’t provide much in the way of additional functionality but it does allow things to be organized in a cleaner way, and as a side effect the applications could still be run standalone in a pinch.
Obviously the intent going forward is to have only the one main application, but it doesn’t seem like the current structure of the project is quite there yet.
Anyway, I know that not all applications follow the model, but it seems like it would be good to try to lay things out in as standard a way as possible, accounting for application needs, of course.
Here’s Apple’s guidelines. Again, I know not everything fits.
https://developer.apple.com/library/ios/documentation/CoreFoundation/Conceptual/CFBundles
Garth
> Hi all,
>
> as Wayne already mentioned below I made some major changes to the creation of OSX application bundles in the build process.
> The most obvious is that now only one application bundle is created which starts the kicad launcher.
> From there you can go anywhere else.
> The created bundle now is (should be) completely relocatable, so you can just put it anywhere you want as with other OSX apps.
> All the pre-delivered templates, etc. have been moved into the bundle and should be found from there.
> Command-Line tools are still contained (and accessible via e.g. /Applications/kicad.app/Contents/MacOS/idf…).
>
> I have uploaded a sample dmg image here:
> http://ul.to/ypsk7m41
> What you see in the dmg is 1:1 what is created in the build process now… this should make packaging and distributing automated builds very easy in future.
>
> I am still doing some final touches to the patch before it gets submitted.
> So, feel free to test and comment…
>
>
> Regards,
> Bernhard
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
Follow ups