Hey everyone,
I’m John (the developer of nEXT (https://github.com/neXT-Browser/nEXT/ https://github.com/neXT-Browser/nEXT/),
I’m trying to produce a standalone binary. I managed to create a “.app” bundle of my application, and then I linked the libraries ecl and eql following this approach (https://stackoverflow.com/questions/2809930/macdeployqt-and-third-party-libr... https://stackoverflow.com/questions/2809930/macdeployqt-and-third-party-libraries):
install_name_tool -change libeql5.1.dylib @executable_path/../Frameworks/libeql5.1.dylib next.app/Contents/MacOS/next install_name_tool -change @libdir@/libecl.16.1.dylib @executable_path/../Frameworks/libecl.16.1.dylib next.app/Contents/MacOS/next
otool then reveals that everything was successful:
otool -L next.app/Contents/MacOS/next
next.app/Contents/MacOS/next: @executable_path/../Frameworks/libecl.16.1.dylib (compatibility version 16.1.3, current version 0.0.0) @executable_path/../Frameworks/libeql5.1.dylib (compatibility version 1.0.0, current version 1.0.0)
Anyways, long story short, I got the following terminal output when I try to launch my new app binary:
In order to minimize the possibility of mistakes in my program, misusage of QT etc, I’ve created a branch where I’ve included only 2 lisp files, a package file, and a “base” file:
https://github.com/nEXT-Browser/nEXT/tree/compile/next https://github.com/nEXT-Browser/nEXT/tree/compile/next
Any ideas on how to proceed would be very useful, thank you,
-John