# Cabbage on Mac

**URL:** <https://forum.cabbageaudio.com/t/cabbage-on-mac/3001>\
**Category:** Cabbage Stew\
**Created:** [23 December 2021 17:56 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001 "2021-12-23T17:56:22Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [23 December 2021 17:56 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/1 "2021-12-23T17:56:22Z")

</div>

Hi Rory,

Cabbage installed with the latest beta installers (after 2.8.69) don’t work on MacOS 10.14.6. I tried also building on MacOS 10.14.6 with this error (not sure if this is informative):

```
-> 0x103b303ae <+10>: jae 0x103b303b8 ; <+20>

dyld: Library not loaded: /Library/Frameworks/CsoundLib64.framework/CsoundLib64
  Referenced from: /Volumes/Data2015/Projects/programming/audio_programming/cSound/Cabbage/installers/cabbage-cmake/cabbage/build/Cabbage_artefacts/Debug/Cabbage.app/Contents/MacOS/Cabbage
  Reason: no suitable image found. Did find:
	/Library/Frameworks/CsoundLib64.framework/CsoundLib64: code signature in (/Library/Frameworks/CsoundLib64.framework/CsoundLib64) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
	/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64: code signature in (/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
(lldb) 

```

Merry Christmas!

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [24 December 2021 09:33 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/2 "2021-12-24T09:33:28Z")

</div>

> [@Samo](#):
>
> Merry Christmas!

The only way I could ensure myself a happy Christmas would be to drop support for Apple entirely ☹ But don’t worry, I won’t be doing that anytime soon.

What’s odd about your output messages is that it’s referencing your own build of Cabbage?

---

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [24 December 2021 10:51 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/3 "2021-12-24T10:51:59Z")

</div>

Yes, I sense the bad Apple, but Cabbage shall prevail! 🙂  
Why is it odd that’s referencing my own build, if I sent you the message from Xcode after running my build? The installers from Azure don’t run.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [24 December 2021 12:30 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/4 "2021-12-24T12:30:25Z")

</div>

Oh sorry, I thought this error was from the public build. For your own build you probably have to sign the Csound framework. Can you try this:

`sudo codesign -s - CsoundLib64.framework --timestamp --deep --force`

All this signing stuff is a nightmare.

---

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [24 December 2021 13:25 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/5 "2021-12-24T13:25:41Z")

</div>

I’m getting this message after trying to sign:  
CsoundLib64.framework: unsealed contents present in the root directory of an embedded framework

Would signing resolve also the Azure builds?  
btw. the latest Mac build (with button border fix) was cancelled.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [24 December 2021 14:09 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/6 "2021-12-24T14:09:16Z")

</div>

> [@Samo](#):
>
> Would signing resolve also the Azure builds?

It’s worth a shot. I don’t sign them in Azure because I haven’t been able to set that up remotely.

> [@Samo](#):
>
> btw. the latest Mac build (with button border fix) was cancelled.

Hmm, I just re-triggered the build now. 👍

[edit] The latest build seems to have completed..

---

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [24 December 2021 16:25 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/7 "2021-12-24T16:25:21Z")

</div>

Thanks! How shall I sign / make it run after the message below?

 ![image](https://forum.cabbageaudio.com/uploads/default/original/2X/0/0ad4e9b0e9686125c4c749f22381deeb124f8bf5.png)

Do you also have any suggestions for “home” building?

> [@Samo](#):
>
> I’m getting this message after trying to sign:  
> CsoundLib64.framework: unsealed contents present in the root directory of an embedded framework

Very sorry to bother you with this, but I don’t know how to enable later beta’s on my system.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [25 December 2021 08:08 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/8 "2021-12-25T08:08:02Z")

</div>

Did you try signing the Cabbage.app bundle?

`sudo codesign -s - Cabbage.app --timestamp --deep --force`

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [25 December 2021 08:58 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/9 "2021-12-25T08:58:51Z")

</div>

I just tried the latest beta package, and it won’t run for me either 🤦 I didn’t have time to investigate but will try later.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [25 December 2021 09:17 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/10 "2021-12-25T09:17:47Z")

</div>

Btw @Samo, are you using a public release of Csound, or one of my Csound packages?

---

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [25 December 2021 10:54 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/11 "2021-12-25T10:54:19Z")

</div>

I believe I’m using your Csound package, since I have Csound ticked for installation in Azure installer. The version doesn’t change when changing from Cabbage ver. 2.8.68 to 2.8.77. The former runs, latter not.

```
--Csound version 6.16 (double samples) Aug 23 2021
[commit: c7601d11f029f24590917d4a1797e247eafdef21]

```

However, signing Cabbage seems to do the trick on the Azure installer 🙂

> [@rorywalsh](#):
>
> `sudo codesign -s - Cabbage.app --timestamp --deep --force`

Is there something similar we can do with “home builds” with Xcode?

I’m happy that I can for now(?) at least use Azure beta updates.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [25 December 2021 10:58 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/12 "2021-12-25T10:58:01Z")

</div>

Nice work 👏 Great that we now have a solution for this. My local builds don’t suffer from the same issue. I wonder if Xcode is signing the app here for me, but not for you? Can you try signing the local build?

---

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [25 December 2021 14:03 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/13 "2021-12-25T14:03:07Z")

</div>

Sorry, but I’m not sure how to sign the local build. The Cabbage.app here gets signed and runs:

 ![image](https://forum.cabbageaudio.com/uploads/default/original/2X/7/762c3eb8cbada4046115ffffae5a33ecaa392d73.png)

But the app seems an older build and I am not sure Xcode actually manages to build:

 ![image](https://forum.cabbageaudio.com/uploads/default/original/2X/1/10485629b1fec48453f289ecd83db590cef6b6c9.png)

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [25 December 2021 15:22 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/14 "2021-12-25T15:22:31Z")

</div>

You need to pull from git in order to get the latest changes. You can also do a clean from the build menu and try again.

---

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [26 December 2021 10:14 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/15 "2021-12-26T10:14:51Z")

</div>

I did pull from git. Still, it doesn’t build - error above.

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [26 December 2021 12:31 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/16 "2021-12-26T12:31:36Z")

</div>

So, it looks like it’s building, but won’t run from within Xcode. Can you sign the application it creates, and then try running it outside of Xcode?

---

<div class="post-metadata">

**Author:** ![Samo](https://forum.cabbageaudio.com/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@Samo](https://forum.cabbageaudio.com/u/Samo)\
**Post date:** [26 December 2021 17:43 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/17 "2021-12-26T17:43:44Z")

</div>

OK. It seems I can sign the app (and it runs through Xcode) now when I found the app in “debug” - I though it would build it in the root where I found an old build. I guess this is all normal? Thanks!!!

 ![image](https://forum.cabbageaudio.com/uploads/default/original/2X/1/1e368cab5ed7fcc6c2a1f6b1006df6bba656d8e9.png)

I got a bit paranoid by Apple’s “lockdown”…  
I hope this doesn’t get worse on the later versions of MacOS. 😨

---

<div class="post-metadata">

**Author:** ![rorywalsh](https://forum.cabbageaudio.com/user_avatar/forum.cabbageaudio.com/rorywalsh/32/165_2.png) [@rorywalsh](https://forum.cabbageaudio.com/u/rorywalsh)\
**Post date:** [27 December 2021 09:41 UTC](https://forum.cabbageaudio.com/t/cabbage-on-mac/3001/18 "2021-12-27T09:41:04Z")

</div>

You and I both. I think that sooner or later they will force everyone to release through the app store 🤬
