Reinhard Tartler <siret...@tauware.de> writes: >>> -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
It most certainly does, for instance in fft.c. -- Måns Rullgård m...@mansr.com _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
