Way to go Adam!
On 2/4/20 5:03 PM, Adam Wolf wrote:
> Hi folks!
>
> Good news.
>
> On my dev machine, I've got the DMG, the apps, all the frameworks,
> everything, all notarized. The apps are all signed even!
>
> We don't need to change the symlinks! (I'm a little bummed that the
> relayed que
My first email to the list about my signing efforts are from early 2017!
On Tue, Feb 4, 2020 at 4:12 PM Jeff Young wrote:
>
> Awesome! Great job, Adam.
>
>
> > On 4 Feb 2020, at 22:03, Adam Wolf wrote:
> >
> > Hi folks!
> >
> > Good news.
> >
> > On my dev machine, I've got the DMG, the apps, a
Awesome! Great job, Adam.
> On 4 Feb 2020, at 22:03, Adam Wolf wrote:
>
> Hi folks!
>
> Good news.
>
> On my dev machine, I've got the DMG, the apps, all the frameworks,
> everything, all notarized. The apps are all signed even!
>
> We don't need to change the symlinks! (I'm a little bumme
Hi folks!
Good news.
On my dev machine, I've got the DMG, the apps, all the frameworks,
everything, all notarized. The apps are all signed even!
We don't need to change the symlinks! (I'm a little bummed that the
relayed question->answer from WWDC wasn't accurate, but that was 3
years ago, and
You are right, Bernhard, that it's weird. I found an issue where I can
reproducibly segfault Apple's codesign!
Ian, maybe hold off on anything drastic re symlinks until I do some more
experimentation. It's possible the question was relayed incorrectly at
WWDC and our setup could work fine...
Ad
I think `kicad --eeschema` would fix this part of the
notarization/signing issue, Ian.
I share Bernhard's concern about letting it work from the GUI too.
I wish I knew Apple's long term plans here. Can we continue to work
on signing and notarization as a low priority thing, or is the next
versio
OK, I see… this is weird.
My understanding from what I read in the documentation was, that it should sign
everything in the top-level bundle (kicad.app) including sub-apps you might
have in kicad.app/Contents/Applications.
Regards,
Bernhard
> On 3. Feb 2020, at 16:47, Adam Wolf wrote:
>
> I
Alright folks, based on this conversation I have at least one or two more
tests to do regarding symlinks.
Second, I'll do some investigating to see what Apple has changed with
notarization today. If we see users having issues, we can assure them that
we're working on it.
Third, I'll update the k
I am not notarizing the DMGs. While this is possible, it has not been
necessary so far.
When I tried notarizing kicad.app but not the others, when I move to a
new computer, it complains that eeschema.app is not notarized.
The problem is not putting the signed kicad.app into an unsigned dmg.
On
Theoretically yes, I guess.
From cmdline it probably would solve the problem and the links together with
those standalone-apps could be removed.
But, from a non-cmdline user perspective:
Is there a way to “wrap” (?) this call to main kicad.app with some parameter
into a nice icon that just looks
Adam (et al.),
If you didn't have to package the single top executable (e.g. eeschema,
pcbnew) would this allow you to remove the symlinks? We have been
discussing adding command line flags to the main kicad executable to launch
the various frames as standalone (e.g. `kicad --eeschema` would launc
Hi Adam,
I am also no fan of the symlinks, but having a different approach will
be probably some work.
I had someone ask if what we do would work during WWDC and I was told
it would not work. I consistently get "the signature is invalid" when
signing while we have symlinks, and when I remove t
Holger,
There already is some OS specific loading stuff in eeschema.cpp. Any
dylibs can probably lice where they are, but plaintext files like ... I
think ciderinit, will have to move.
I'll setup a gitlab issue for us to coordinate
Thanks!
Adam
On Mon, Feb 3, 2020, 4:44 AM Holger Vogt w
Bernhard,
I have no personal vendetta against the symlinks.
I had someone ask if what we do would work during WWDC and I was told it
would not work. I consistently get "the signature is invalid" when signing
while we have symlinks, and when I remove the symlinks and just sign
KiCad.app this erro
I will have a look at the ngspice issues. I guess that the only files
that we really need in the distribution (besides the ngspice dylib) are
the codemodel *.cm files. They are also dylibs to be loaded dynamically
into ngspice. The commands to load these files (including path
information) is se
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
To be more explicit, for ngspice for #2) how do we move the
Contents/Plugins/sim/ngspice directory to Contents/Resources/ngspice
*and* get ngspice to know where it is?
On Sun, Feb 2, 2020 at 7:00 PM Adam Wolf wrote:
>
> Hi folks!
>
> Apple is changing how the lack of notarization looks like to us
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 signatu
18 matches
Mail list logo
