Standalone missing library

Cabbage slugs
1

Hi all,

M1 Pro MBP 32/1T Tahoe 26.2 / Cabbage version:2.9.0

My project exports fine as a Logic Pro plug-in, but when I try to create a standalone version the app fails to launch and its icon uses that circle-slash that indicates a compatibility issue.

Opened up the package and ran the executable, which returns the following:

Last login: Tue Jan  6 17:40:29 on console

lfrancis@lfrancis-3s-mc-01 ~ % /Users/lfrancis/Pictures/killme/CeeS\ Cntrl.app/Contents/MacOS/CeeS\ Cntrl ; exit;

dyld[8623]: Library not loaded: /Library/Frameworks/CsoundLib64.framework/CsoundLib64

  Referenced from: <4A9E24E0-35E8-376D-9E72-CAEDBCCDFC6C> /Users/lfrancis/Pictures/killme/CeeS Cntrl.app/Contents/MacOS/CeeS Cntrl

  Reason: tried: '/Library/Frameworks/CsoundLib64.framework/CsoundLib64' (code signature in <DC83FEAD-0AD9-3CAE-BB5B-F90873DDF038> '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Volumes/Preboot/Cryptexes/OS/Library/Frameworks/CsoundLib64.framework/CsoundLib64' (no such file), '/Library/Frameworks/CsoundLib64.framework/CsoundLib64' (code signature in <DC83FEAD-0AD9-3CAE-BB5B-F90873DDF038> '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Library/Frameworks/CsoundLib64.framework/CsoundLib64' (no such file, not in dyld cache), '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' (code signature in <DC83FEAD-0AD9-3CAE-BB5B-F90873DDF038> '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Volumes/Preboot/Cryptexes/OS/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' (no such file), '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' (code signature in <DC83FEAD-0AD9-3CAE-BB5B-F90873DDF038> '/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Library/Frameworks/CsoundLib64.framework/Versions/6.0/CsoundLib64' (no such file, not in dyld cache)

zsh: abort      /Users/lfrancis/Pictures/killme/CeeS\ Cntrl.app/Contents/MacOS/CeeS\ Cntrl



Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.

Deleting expired sessions...       8 completed.



[Process completed]

Assuming the missing library is the issue, but as the au plug-in version can find it, maybe this is a bug? Cheers!

2

That’s odd, nothing would run if Csound was missing. Have you tried code-signing the app? Also, does this help:

3

Thanks, that other post you referenced is how I got the terminal results, but I didn’t get as far as they at the get-go because the app won’t launch. Here’s what it looks like with the circle-slash I mentioned. I’ll look into what’s involved with ad-hoc code signing apps.

image
image278×288 44.4 KB

1 Like
4

Ok, code signing the app results in the same behavior reported in that other post. I still get the circle-slash over the app icon but when I open the package and run the executable, it now launches.

What do we need to do to make the standalone open as expected?

5

Once it launches once, I think it should be able to launch again from the icon? It’s a while since I looked at the standalone builds. They don’t seem to be used that often.

6

Sadly, that doesn’t seem to be the case. Plus we still have that pesky circle-backslash icon to deal with.

7

Can you try opening your settings, and going to privacy sectury, and see if it’s not listed at the very bottom, you might be able to select allow to run or something like that? Oh crap, i just realised you’re still using quite an old version of Cabbage. Can you try one of the latest builds?

However over the installers item and you’ll see three dots appear on teh right, click that to download the latest installers.

1 Like
8

Yup, 2.10.0 exports my standalone w/o issue – thanks! Now off to see if any of my weirdo Logic Pro plug-in issues have also gone away. :wink:

1 Like
9

Not weirdo Logic Pro plug-in issues, just noob stuff. :wink:

1 Like