You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to launch the uae-dap adapter when installed globally via NPM on macOS is causing a dynamic loader error, at least on my system:
dyld[10852]: Library not loaded: @loader_path/../../../../opt/freetype/lib/libfreetype.6.dylib
Referenced from: <07B03B30-1437-3451-BA21-71A9F664B841> /opt/homebrew/lib/node_modules/uae-dap/bin/fs-uae/lib/libharfbuzz.0.dylib
Reason: tried: '/opt/homebrew/lib/node_modules/uae-dap/bin/fs-uae/lib/../../../../opt/freetype/lib/libfreetype.6.dylib' (no such file), '/usr/local/lib/libfreetype.6.dylib' (no such file), '/usr/lib/libfreetype.6.dylib' (no such file, not in dyld cache)
This appears to be because the libfreetype.6.dylib library and its siblings are one level deeper than the specified path relative to @loader_path.
I did a quick regression test of versions, and it appears this was introduced at v1.0.3 of uae-dap, as installing v1.0.2 fixes it and the adapter launches properly.
If I can provide any additional information, or might've missed something obvious, let me know!
The text was updated successfully, but these errors were encountered:
logancollins
changed the title
Adapter fails to launch FS-UAE on macOS due to incorrect dynamic library paths
Adapter fails to launch on macOS due to incorrect dynamic library paths
Dec 21, 2023
Trying to launch the
uae-dap
adapter when installed globally via NPM on macOS is causing a dynamic loader error, at least on my system:This appears to be because the
libfreetype.6.dylib
library and its siblings are one level deeper than the specified path relative to@loader_path
.I did a quick regression test of versions, and it appears this was introduced at v1.0.3 of
uae-dap
, as installingv1.0.2
fixes it and the adapter launches properly.If I can provide any additional information, or might've missed something obvious, let me know!
The text was updated successfully, but these errors were encountered: