If you try and run ./configure with --enable-nuv then it is a
requirement that you specify --enable-lzo to go with it. However, the
check for this dependency is made rather late and probably should have
been done before the guts of ./configure ran at all.
You get the message:
configure: error: liblzo2 is required for NuppelVideo support, try
--enable-lzo
but only after lots of ./configure output about testing for all sorts of
libraries and other things. It should probably have complained before
even running one of the tests, being as this is a command-line requirement.
--------------------------------------------------------------
Now, the same error message comes up even if you *did* specify
--enable-lzo but don't happen to have liblzo2 installed on the compile
machine. This is just a minor grumble, I agree, but would it not have
been good to spot that the user specified --enable-lzo and crash out of
./configure as soon as the following happens:
checking whether libquicktime support is requested... no
checking whether lzo support is requested... yes
^^^^^
so.. ./configure know that it wants lzo (or is that lzo2?)
checking for pkgconfig support for lzo... no
checking how to determine LZO_CFLAGS... default
checking lzo/lzo1x.h usability... no
checking lzo/lzo1x.h presence... no
checking for lzo/lzo1x.h... no
checking how to determine LZO_LIBS... default
checking for lzo_version in -llzo2... no
I'd expect a stop here. User requested lzo and we've not got the
library. Instead it carries on with:
checking whether a52 support is requested... no
..and a million other checks, and much later crashes with:
checking for NuppelVideo support...configure: error: liblzo2 is required
for NuppelVideo support, try --enable-lzo
Confusing, because of course the user *did* specify --enable-lzo in the
first place.
Steve
