On Wed, Dec 31, 2014 at 02:09:42PM +0100, Nicolas George wrote: > Le primidi 11 nivôse, an CCXXIII, Reimar Döffinger a écrit : > > I don't care much, but I still find not having to use pkg-config > > somewhat more convenient in a cross-compilation environment where > > you don't want to install all dependencies just to make it work with > > pkg-config (or alternatively manually hack those files). > > Can you elaborate on that? I suspect there are ways of making this work > easily with pkg-config, but you are to vague about the dependencies you want > to avoid, so I can not suggest a way.
If I just download libspeex, libfdk_aac, libsdl etc. and build them with CC=i686-mingw32-gcc ./configure, then without pkg-config I can just add a few paths to -I and -L and I can link against them. With pkg-config things tend to get inconsistent and more complicated. For example some programs (no, I haven't tried lately so I don't remember examples) generate them only on install, so you have to make install. But to do that you have to figure out how to specify a install directory. Even if they don't, you still have to add the .pc paths in addition. >From my point of view it's only more convenient if all you want to use are things that are pre-packaged by your distribution. Btw. would you be less opposed to a patch that added less obfuscation? It looks to me like we would just require an extra "fallback -l" option (preferably also a fallback extra cflags one) to use_pkg_config to allow hiding all the extra complexity in one place, inside that function. I agree that it gets messy if we add a special case to more and more places. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
