ср, 11 февр. 2026 г., 17:46 Terje J. Hanssen <[email protected]>:
On 2/11/26 2:48 PM, Terje J. Hanssen wrote:
On 2/11/26 2:32 PM, Andrew Randrianasulu wrote:
...........snip
--------------
8) Build procedure further from here?
Where does the bld_dynamic.sh script fit in?
./configure --with-single-user --disable-static-build --without-thirdparty
(there are some typos in the manual: "confgure" instead of "configure" pdf page 12, 13. 653)
setting CFLAGS?
should not be necessary, but you can try and see if it fails :)
I think --with-single-user is safer, and you can use
bld_appimage.sh
for appimage-ing result of (hopefully successful) compilation.
Note, I did not tried this with dynamic cingg build ... Hopefully appimagetool will only add loaders and not whole .. hw driver stack.
I think blds/bld_dynamic.sh is maintainer script more than user script
It was not updated to new git protocol (https vs git)
So you probably can skip it and just manually use your "--without-thirdparty --with-single-user --disable-static-build" configure line, and then make and make install
test and appimage it
Or possibly a configure line like this to include link to my system ffmpeg?
"--without-thirdparty --with-single-user --disable-static-build --with-ffmpeg=/usr/bin/ffmpeg"
or possibly?
./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx --with-external-ffmpeg
or alternatively (not sure about what is valid syntax) ?
./configure --with-single-user --disable-static-build --without-thirdparty --without-libdpx --with-systeml-ffmpeg
you can use configure --help to see supported arguments. I had idea about adding configure switch (in addition to env variable?) to pick up libav* libs from standard location, but this idea only lives in my head for now.
_________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]