Hi Hannah, Something changed in the craft build of FFMPEG between May 2nd and May 4th. We are now getting this error when packaging KStars on Binary Factory. https://binary-factory.kde.org/view/MacOS/job/KStars_Nightly_macos/ <https://binary-factory.kde.org/view/MacOS/job/KStars_Nightly_macos/>
The last successful build was May 2nd. [2022-05-05T17:22:22.892Z] /Users/packaging/Craft/BinaryFactory/macos-64-clang/build/kde/applications/kstars/archive/Applications/KDE/kstars.app/Contents/Frameworks/libavdevice.59.4.100.dylib: don't know how to handle otool -L output: '/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/ffmpeg/image-RelWithDebInfo-5.0.1/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib' It looks to me like there is a linking issue. For some reason, the (nonexistent) path for libavfilter stored in libavdevice is: '/Users/packaging/Craft/BinaryFactory/macos-64-clang/build/libs/ffmpeg/image-RelWithDebInfo-5.0.1/Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib' When it should be either /Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib Or @rpath/libavfilter.8.dylib In fact all the other ffmpeg dylibs are linked like this: /Users/packaging/Craft/BinaryFactory/macos-64-clang/lib/libavfilter.8.dylib It is just that one that is wrong. Was there some sort of craft change which would break this? Thanks, Rob
smime.p7s
Description: S/MIME cryptographic signature
