Single app build for MacOS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Released
|
Unknown
|
Bug Description
I discussed this with Adam a bit at KiCon -- we should investigate moving to a single app package on MacOS rather than a bundle with each KiCad tool as its own app inside the bundle.
This may be required for Apple notarization. It will also have side-effects of improving packaging time. We'll need to add some handling for file open targeting (drag and drop, etc) and provide command-line argument support for launching from the KiCad host into a single target application when the main KiCad (project manager) is not chosen to open by the user.
Somewhat related to lp:1753071
Setting as Wishlist for now but the priority might get bumped up if it turns out this is the only way to pass notarization by Apple.
Changed in kicad: | |
milestone: | none → 6.0.0-rc1 |
importance: | Undecided → Wishlist |
status: | New → Triaged |
description: | updated |
tags: | added: macos packaging |
Changed in kicad: | |
importance: | Wishlist → Unknown |
status: | Expired → Fix Released |
What needs to be done to make this happen? I'm assuming at a minimum the gerber viewer, worksheet editor, calculator, and bitmap converter applications would have to be retooled to be child windows of KiCad instead of running in separate processes. To be honest, I'm not sure how this would fly. I know there are quite a few users who prefer to run Eeschema and Pcbnew as stand alone apps so I wouldn't see why this would be any different on macos. I'm not opposed to doing this but we should you the Kiway interface so we can keep them as separate apps on other platforms.
Is it possible that we are missing something with the macos signing that would allow us to use our current design? I don't pretend to know anything about macos (the gift that keeps on giving) so I'm just playing the devils advocate here. Maybe there is something we are over looking that would make our life easier.