[Libav-user] Windows compile can't find LAME

[Carl Eugen Hoyos]

2018-07-08 18:46 GMT+02:00, Jeremy Gregorio
<gunvalkyrie-at-yahoo.com at ffmpeg.org>:
>  ./configure --toolchain=msvc --arch=i386 --enable-yasm --enable-asm
> --enable-static --disable-shared --enable-libx264 --enable-libmp3lame
> --enable-gpl --extra-ldflags=-L/usr/lib --extra-cflags=-I/usr/include/lame
> --host-ldflags=-L/user/lib   --extra-libs=-lm --extra-libs=-lpthreads

Unrelated:
The following options are useless because they are the default and
make debugging the configure line more difficult:
--enable-yasm --enable-asm --enable-static --disable-shared

If the following is unneeded (as I expect), it is dangerous to use it
(most people do not understand what the option does):
--arch=i386

I know that there is a (horrible) regression that makes -lm and -lpthreads
sometimes necessary, it would still be great if you could report why it is
needed in your case.

> But it complains it can't find lame:
>     ERROR: libmp3lame >= 3.98.3 not found

(Not unrelated:)
Was this the only line printed by configure when it failed
or was there anything else?

Carl Eugen