So in order to get Apple’s debugger (or LLVD for that matter) to link while I develop, I need to compile SC from scratch. I followed the very clear and detailed instructions here after checking out the tag at 3.13.0 because it is the latest public version. After a little churning, I get the build succeeded message, hurray!
But. Doubleclicking on the app in ./Install, I get an instacrash - happily I’m in RelWithDebInfo so here goes:
Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: ‘@loader_path/…/…/…/QtQuickWidgets.framework/Versions/5/QtQuickWidgets’
Referenced from: ‘/Users/USER/Documents/*/SuperCollider.app/Contents/Frameworks/QtWebEngineWidgets.framework/Versions/5/QtWebEngineWidgets’
Reason: tried: ‘’ (no such file), ‘’ (no such file), ‘’ (no such file)
(terminated at launch; ignore backtrace)
it seems that following the instructions à la lettre it finds QT5 all right to compile but not enough to run? Or have I missed something?
(the good news is that the server is functional so I can run that and debug my plugins )
Any pointers of what is wrong with me, or the read me, welcome.
(I have found and documented a way to work without the full comping process here using only a custom scsynth but it would be good to find what is happening I reckon for other people so if you want I’m happy to continue to try to get it to work)
My apologies if you already knew this, but -D settings persist in the build directory. Turning off QtWebEngine is cmake .. -DSC_USE_QTWEBENGINE=OFF, turning it back on requires cmake .. -DSC_USE_QTWEBENGINE=ON. Unfortunately I’m not sure how to troubleshoot the issue
I know, I even completely deleted the content of the build folder to avoid any gremlins… to no avail. If I’m the only one with issues then let’s not lose time on this - I’m functional with the downloaded IDE and compiling just the server to troubleshoot
I had problems on macOS when I had both Qt5 and Qt6 (aka the default Qt) installed. I believe homebrew Qt6 is linked to system locations by default, in contrary to Qt5.
If you indeed have Qt6 installed, I’d try to unlink it (brew unlink qt6), clear the build directory, then cmake configure and build again.
thanks @MarcinP - brew list tells me I have qt@5 and not qt6 or anything like that… I just reinstalled the system on this machine, it is super new, so it is a good test for such instructions I reckon