Build issue on Catalina: how to fix dylib paths in pre-built executables? `install_name_tool: internal error: swap_object_headers() failed`

[barracuda156]

Pre-compiled binaries fail to get fixed by install_name_tool:

** INSTALL SUCCEEDED **

error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: in swap_object_headers(): malformed load command 0 (cmdsize is zero)
fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: internal error: swap_object_headers() failed
Command failed: install_name_tool -change /usr/local/lib/libfuse.0.dylib /opt/local/lib/libosxfuse.dylib /opt/local/var/macports/build/macfusion2-863a57c4/work/destroot/Applications/MacPorts/Macfusion.app/Contents/PlugIns/ftpfs.mfplugin/Contents/Resources/curlftpfs_static_mg
Exit code: 1

Existing dylib paths point to Homebrew prefix, so they break executables with MacPorts installation.

[ElDeveloper]

hi @barracuda156, I don't have much input to provide here except that we do not have the macports or homebrew recipes in this repository.

[barracuda156]

There are a few binaries used in the repo which do not have sources available so can’t be compiled. They have baked in paths to libfuse and/or libosxfuse in /usr/local/lib. My question is how to fix those paths to point to a correct locations. install_name_tool fails on Catalina with error I quoted.

[ElDeveloper]

If memory serves right, there's a path that's hardcoded in the source that checks for the OS and passes the correct path as needed. But I think as you said the better option would be to make these targets of the project and compile as needed.