Details
-
Bug
-
Resolution: Fixed
-
Not Evaluated
-
2.3.1
-
None
-
-
70e60671e (2.4)
Description
The the small attached example project creates a universal dylib by combining two prebuilt binaries and use it to build a universal app on macOS.
The build command used is
> qbs build config:debug profile:qt6_6@macos qbs.architectures:arm64,x86_64 -f app.qbs --build-directory ../universal-test
which builds the app without errors (and uses lipo) and produces this install-root layout (dSYM omitted):
./bin
./bin/app
./lib
./lib/libfmt.11.0.0.dylib
./lib/libfmt.dylib
However, app cannot start because the app is linked to "libfmt.11.dylib" rather than "libfmt.11.0.0.dylib" or "libfmt.dylib".
Basically this is right because the install-name of the libfmt.dylib is "libfmt.11.dylib".
But qbs does not seem to create the required symlink "libfmt.11.dylib", just "libfmt.dylib".
I've checked that createSymLink is true and the soVersion is also determined correctly inside the cpp module, so i think it should create the missing symlink as well, but does not.