On Thu, 2011-04-21 at 06:47 +0200, Reinhard Tartler wrote: > On Wed, Apr 20, 2011 at 20:06:11 (CEST), Måns Rullgård wrote: > >> -pkgconfig_generate libavutil "Libav utility library" "$LIBAVUTIL_VERSION" > >> +pkgconfig_generate libavutil "Libav utility library" "$LIBAVUTIL_VERSION" > >> "$LIBM" > >> pkgconfig_generate libavcodec "Libav codec library" "$LIBAVCODEC_VERSION" > >> "$extralibs" > >> pkgconfig_generate libavformat "Libav container format library" > >> "$LIBAVFORMAT_VERSION" "$extralibs" "libavcodec = $LIBAVCODEC_VERSION" > >> pkgconfig_generate libavdevice "Libav device handling library" > >> "$LIBAVDEVICE_VERSION" "$extralibs" "libavformat = $LIBAVFORMAT_VERSION" > >> pkgconfig_generate libavfilter "Libav video filtering library" > >> "$LIBAVFILTER_VERSION" "$extralibs" > >> -pkgconfig_generate libpostproc "Libav post processing library" > >> "$LIBPOSTPROC_VERSION" > >> -pkgconfig_generate libswscale "Libav image rescaling library" > >> "$LIBSWSCALE_VERSION" "" "libavutil = $LIBAVUTIL_VERSION" > >> +pkgconfig_generate libpostproc "Libav post processing library" > >> "$LIBPOSTPROC_VERSION" "" "libavutil = $LIBAVUTIL_VERSION" > >> +pkgconfig_generate libswscale "Libav image rescaling library" > >> "$LIBSWSCALE_VERSION" "$LIBM" "libavutil = $LIBAVUTIL_VERSION" > >> -- > >> 1.7.0.4 > > > > Why add libm to those specific files? libavcodec most definitely uses it. > > because pkg-config resolves dependencies recursively. libavcodec does > not seem to use libm directly
I think it shouldn't really matter whether any of the libraries that already depend on libavutil explicitly depend on libm for static linking or not. The libavcodec -> libavutil -> libm dependency chain already forces -lm to appear after -lavcodec on the linker command line (-lm must appear after -lavutil which must appear after -lavcodec). _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
