ChanServ changed the topic of #ffmpeg to: Welcome to the FFmpeg USER support channel | Development channel: #ffmpeg-devel | Bug reports: https://ffmpeg.org/bugreports.html | Wiki: https://trac.ffmpeg.org/ | This channel is publically logged | FFmpeg 7.1.1 is released
JustBleedFan has joined #ffmpeg
<matteobin>
How does FFmpeg configure autodetect a library? How can I tell it to load a shared library from elsewhere?
<JEEB>
it looks up the development headers and stuff usually, which most often is done through pkg-config (which nowadays tends to be a symbolic link towards pkgconf), which follows PKG_CONFIG_LIBDIR and PKG_CONFIG_PATH
<JEEB>
(_PATH actually appends and doesn't override, which is different from just setting PATH=xyz)
MyTDT_ has joined #ffmpeg
<JEEB>
usually if you're dealing with shared libraries unless you have rpath the standard dynamic library loading logic of whatever operating system is followed
lavaball has joined #ffmpeg
<matteobin>
Thank you. :)
<JEEB>
so if the issue is not build time but just runtime, then you need to fix the runtime loading paths
<JEEB>
if it's a problem at build time, then you stare at ffbuild/config.log in your build directory and attempt to figure out what it actually tried to poke instead of what you wanted it to poke
<JEEB>
(I had some fun recently with some february 2024 vulkan headers in my custom sysroot due to needing newer headers then than packaged)
<JEEB>
and the configure check would actually catch the system ones and thus pass or something like that :P
<JEEB>
-> build-time header look up would catch the other one
MyTDT_ has quit [Ping timeout: 260 seconds]
<matteobin>
Thank you for the help. :)
lavaball has quit [Remote host closed the connection]
lavaball has joined #ffmpeg
Traneptora has quit [Remote host closed the connection]