[opensource-dev] macOS Catalina notarization

Apple has tightened up their criteria for notarizing apps. For those of you not familiar with the issue, the current version of macOS, 10.15 Catalina, makes the user jump through some scary hoops to run an application they've downloaded unless it's been notarized - signed with an Apple Developer ID

Re: [opensource-dev] macOS Catalina notarization

On Sat, 29 Feb 2020 10:33:52 -0600, Tonya Souther wrote: > 305 of those libraries are in llplugin, and five are in the SLvoice > for OpenSim. I don't expect that LL has anything to do with the > latter, but the former is the much bigger problem. Is the llplugin > directory still needed? My bet is

Re: [opensource-dev] macOS Catalina notarization

I've now built a VLC 3.0.8 package, and it at least allows the app to be notarized. Haven't wrung it ot yet; not sure I know how, but our beta testers will, I'm sure, let me know if it's screwed up. On Sat, Feb 29, 2020 at 12:18 PM Henri Beauchamp wrote: > On Sat, 29 Feb 2020 10:33:52 -0600, Ton

Re: [opensource-dev] macOS Catalina notarization

It is not only that you have unsigned libraries, but there are two other issues: 1. The Chromium Framework is not correctly structured, but must have the structure described in https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/FrameworkAnatomy.htm

Re: [opensource-dev] macOS Catalina notarization

When it comes to deployment target, I see that in https://bitbucket.org/lindenlab/build-variables/src/master/variables which I suppose is the latest build variables used, you build with deployment target of 10.7 and with th

Re: [opensource-dev] macOS Catalina notarization

I was able to get a successful notarization. I did not have to do anything to CEF to get it to fly, though I did have to use the --options runtime flag. We'll see what testing reveals as the effect of that. That they tightened down things as of the beginning of February explains why the notarizati