hi lucas, > if I don't codesign/notarize the builds: is just that users have an "open > anyway" dialog? or is it a total "show stopper" that quits Pd? its a bit more than just that (sigh), but not a complete show stopper.
i fully symphatize with your take on that, even if it means i will have to hop thru the (firey) loops, apple is setting up to letting me allow running your code on my machine. for us as a community we should probably start thinking how we can pool ressources, so that developers who don´t have / don´t want an apple dev account etc. can still provide their work to the community. if i understood correctly, apples firewall around its ecosystem will be getting even harder to overcome with the next system (ventura) and who knows, whats in the pipeline after that. my 2 (unhelpful) cents hans > Am 11.10.2022 um 19:12 schrieb Lucas Cordiviola <lucard...@hotmail.com>: > > @ Dan > > Thanks for sharing this. I'll be digging about ` you need an Apple Developer > account (and Apple ID to sign up for one)`. If there's no workaround about > the us$100 i'll be giving up notarizing builds. Do you know of a way to not > send money to the thieves (if i'm not mistaken) ? > > or to put it in another way: > > if I don't codesign/notarize the builds: is just that users have an "open > anyway" dialog? or is it a total "show stopper" that quits Pd? > > Which way should I go without the $100 ? > > > -- > > Mensaje telepatico asistido por maquinas. > > On 11/10/2022 12:55, Dan Wilcox wrote: >> Howdy Lucas, >> >> I have the makefiles working but realize now I need to do some refactoring >> to better handle non-app bundles like dylib libraries. Apparently the >> notarization process is a little different. In any case, you can check them >> out for now but I will be working on them further: >> >> https://github.com/zkmkarlsruhe/mac-app-builder >> >> Yes, you need an Apple Developer account (and Apple ID to sign up for one) >> in order to create the certificates for code signing as well as >> notarization. The overview is in the readme. >> >> The notarization process for dylibs appears to be: >> >> * build the dylibs (in our case pd externals) >> * codesign them >> * notarize them (upload to Apple notarization server) >> * package them into a disk image .dmg >> * sign the dmg >> * staple the dmg with the notarization ticket >> >> Distributing via zip will not work in this case because the zip cannot be >> signed like a dmg. >> >> I think it might make sense for us to make a Makefile.pdlibnotarizer or >> something similar. >> >> I also have a separate repo with example programs (Cocoa, openFrameworks, >> console + dylib) for testing, but it's not ready yet. I managed to get the >> dylib signed this morning which is when I found out my assumptions for the >> whole process are different between apps and libs. :( >> >>> On Oct 11, 2022, at 4:48 PM, Lucas Cordiviola <lucard...@hotmail.com> wrote: >>> >>> @ Dan >>> >>> I'm back on my "machines home". I did: >>> >>> xcrun notarytool >>> >>> and I got its help options. >>> >>> Do I need an `apple developer` account ? >>> >>> I don't even have an `apple id`. >>> >>> How should I proceed? do I wait for your script? do i get my `apple id`? >>> >>> I'm sure I'm not the only one willing to provide arm64 builds (pd-porres >>> has already inquired me on this). >> >> -------- >> Dan Wilcox >> @danomatika <http://twitter.com/danomatika <http://twitter.com/danomatika>> >> danomatika.com <http://danomatika.com/> <http://danomatika.com >> <http://danomatika.com/>> >> robotcowboy.com <http://robotcowboy.com/> <http://robotcowboy.com >> <http://robotcowboy.com/>> >> >> >> > > > > _______________________________________________ > Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > <https://lists.puredata.info/listinfo/pd-list>
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
