> On 10 May 2019, at 10:49 am, kee nethery via use-livecode > <use-livecode@lists.runrev.com> wrote: > > > >> On May 9, 2019, at 5:42 PM, Monte Goulding via use-livecode >> <use-livecode@lists.runrev.com <mailto:use-livecode@lists.runrev.com>> wrote: >> >> Looks like the hardened runtime needs —options=runtime > > Which what terminal command would —options=runtime be used? > > From what I can see, the only place to enable hardened runtime is with > projects in Xcode and … this is not a project in Xcode, right?
I’m fairly sure Xcode is just adding it when it executes codesign > >> >> https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/resolving_common_notarization_issues?language=objc >> >> <https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/resolving_common_notarization_issues?language=objc><https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/resolving_common_notarization_issues?language=objc >> >> <https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/resolving_common_notarization_issues?language=objc>> >> >> For the others are you using —force —deep to ensure you replace any existing >> code signatures? > > yes. Learning lots about codesign and xattr and spctl but am really just a > code monkey pressing keys hoping for Shakespeare. Haha… well we all feel like that sometimes! Cheers Monte _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
