[Csnd-dev] Signing MacOS bundle
Tarmo Johannes <[email protected]> Fri, 5 Sep 2025 00:37:33 +0300
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <CAPvdOzAiCc9Trsw=qz0RcmoBA2yCuR5LzQNWz3Oa0zCzpOkhYw@mail.gmail.com> |
Hi! I managed to get a signed tryout MacOS bundle of CsoundQt7+Csound7 done (this is really a tryout but can be usable): https://tarmo.uuu.ee/owncloud/index.php/s/BgNpnqnSRjqXSy1 It is based on Csound7-beta.8, downloaded from Github actions artifacts. What I noticed: - $APP/Contents/Frameworks/CsoundLib64.framework/Versions/7.0/CsoundLib64 gave at first an error: 'code has no resources but signature indicates they must be present '. I needed to remove the signature and resign again. I don't know if it requires attention from Csound side. - the *libs* folder in CsoundLib64.framework folder causes signing error 'Unsealed contents present in the root directory of an embedded framework' - see https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/FrameworkAnatomy.html I needed to move the *libs *folder away from framework root and placed it to resources next to opcodes' dir. I did not do the install_name_tool changes as the libraries were only for portmidi. It would be nice to have the framework immediately with suitable structure so it easy to develop MacOS apps based on it. What do you think? tarmo