>>In other words, it's just an example in the wiki. It's one way to do it, but >>that doesn't mean it's *the* way to do it. Building against dynamic libs is >>certainly much more common if those are (at least for the most part) provided >>by the "system" (distribution or what have you). >> >>Both options must work.
Thanks a lot, this makes sense. I thought that flag was compulsory and therefore we only included linking against libraries in "Libs.private" in the pc file. I have just pushed a fix to the Turing repo to include that in the Libs as well. I have tested this and it seems to work fine in my machine and in the Docker with Ubuntu and debian with and without the flag now. No changes are needed to the actual patch, it should work as long as you update Turing to the latest commit. Thanks a lot for your help with this, Saverio _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
