That’s an interesting use-case you brought. I replied in the linked issue on how to achieve what you want.
Ivan > 13 июля 2024 г., в 13:21, Maximilian Hrabowski <hrabow...@bee360.com> > написал(а): > > > Hi all, > > i use qbs on macos to combine arm64 and x86_64 library builds into one > universal library. My application compiles and links, but cannot start > because the install names/lib names used when linking the app are not correct > – or – basically they are correct but when combining the builds using lipo, > no corresponding symlinks are created. So there is a symlink missing thus the > app fails to load the library at start up. > > E.g. > > Library file name of prebuild binaries is “libfmt.11.0.0.dylib”, there are > symlinks “libfmt.dylib” and “libfmt.11.dylib” in the original single arch > builds > Qbs created the universal lib “libfmt.11.0.0.dylib” and a symlink > “libfmt.dylib” but NO symlink “libfmt.11.dylib” > The app is linked using the intall-name “libfmt.11.dylib” > > App cannot start because “libfmt11.dylib” cannot be found > > I could now manually create the missing link on deployment, but… > > Is there is a way to explicitly create the missing symlink with qbs? > > I created a bug report to illustrate the problem: > https://bugreports.qt.io/browse/QBS-1797 > > Cheers, > Maxim > > _______________________________________________ > Qbs mailing list > Qbs@qt-project.org > https://lists.qt-project.org/listinfo/qbs
_______________________________________________ Qbs mailing list Qbs@qt-project.org https://lists.qt-project.org/listinfo/qbs
