Hi Adam,
I still don’t get it:
Our current
strategy of symlinking into the kicad.app bundle does not work
with
macOS signing.
Xcode has e.g. Instruments application in
Xcode.app/Contents/Applications/Instruments.app
If I symlink it (for example) to
/Applications/Instruments.app
It runs without any complaints when started via the symlink.
What do you notarize?
The overall dmg with the symlink?
Have you already tried to only notarize kicad.app (no dmg, no
symlinks) and put it into the dmg with symlinks afterwards?
Another quick fix could be some script that can be run to create the
symlinks on user machine?
A simple copy of the apps won’t work.
You need to change everything wrt shared libraries in KiCad code and
cmake script.
In the end, you will duplicate all libraries and support stuff.
Probably not a big deal for eeschema and the other small apps, but I
guess for pcbnew.
Means duplicating all the python, nags-ice, etc. stuff.
And also, all stuff like templates, scripts, etc.
Users shouldn’t fiddle around in the .app, but could get really
messy if they now put (template, python, spice?) stuff in kicad.app
or pcbnew.app and then something doesn’t work in one or the
other...
Regards,
Bernhard
On 3. Feb 2020, at 02:00, Adam Wolf
<adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi folks!
Apple is changing how the lack of notarization looks like to users
on
Catalina starting tomorrow. It is not clear what will happen when
folks download new versions of KiCad after tonight.
For the past two months I've been working hard--I've got a tech
demo
locally here that has signatures and notarization on macOS, but
it's
not ready for primetime. For instance, I have removed the other
.apps
and just have kicad.app. There's changes I made to kicad that
probably belong in kicad-mac-builder--and, well, let's just say
it's a
tech demo :)
The main things that remain are:
1) Figure out a good solution for the symlinked .apps. Our
current
strategy of symlinking into the kicad.app bundle does not work
with
macOS signing. I think the current contender is to copy instead
of
symlink. I am not sure how much extra space that will take up but
it's a good try. This is definitely something I can do, but since
it's something that can be done on its own, it's a prime contender
for
someone looking to help out.
2) Another issue is that there are strict rules about where in the
bundle code, data, and executable non-Mach-O files live. For
instance, one of the signing blockers is ngspice, because it
mingles
scripts and Mach-O binaries and then we put them in
Contents/Plugins.
For more details, see
The big change for KiCad itself is where the Python scripts are
stored--I've fixed this in my branch, but now I have to go through
and
audit and fixup our partner packages, like OCE/OCC and ngspice.
If
you want to help with this, it's going to be a big job but I'm
willing
to put in the time to teach if you're willing to put in the time
to
learn :)
I was really hoping I could get this done before Apple turned up
the
enforcement on notarization, but that's going to happen. After
tomorrow, it'll be clearer what Apple is doing. There might be
some
quick changes to make that will improve things for our users
without
getting all of this done.
Adam Wolf
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
