> -----Original Message----- > From: Francesco Romani [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 18, 2008 2:57 AM > To: transcode Developers Mailing List > Subject: Re: [transcode-devel] Compilation issues with plugins > > > On Mon, 2008-03-17 at 17:26 -0400, Jacob (Jack) Gryn wrote: > > Hi, > > > > Hi, thanks for your report. :) > > > a) a lot of packages are installed by default in /usr/local; maybe > > configure could check there also by default (possibly also checking > > the lib64 directories as well on x86_64) > > The intended behaviour of transcode is to disable by default all extra > modules; the ide abehind this decision is that the user should > explicitely enable what it needs, in order to minimize the > dependencies. > So, the configure script not even looks for anything in /usr/local.
I guess I should clarify my question to say this. When I say ./configure --with-modulename, rather than having to explicitly say to look in /usr/local/include or /usr/local/lib; if I say --with-module, it should automatically check the other 'default' directories. > > > b) import/export_mov seem to look for quicktime header files in the > > main includes directory and it does not seem to respect > > --with-quicktime-includes=/usr/local/include/lqt, I manually edited > > them to #include <lqt/???.h> (adding the lqt/); also keep in mind it > > seems that some older files kept it in include/quicktime/*.h but now > > include/lqt/*.h ; in addition; --with-quicktime-prefix in configure, > > should suffice and I shouldn't need to do --with-quicktime-includes > > I'll take a deeper look at this. > > > c) mpeg2dec has 2 libraries, mpeg2 and mpeg2convert. The makefile in > > the import directory has -lmpeg2, but no -lmpeg2convert > > Will be fixed > > > d) something is lame about lame, it insists on the LD_LIBRARY_PATH > > being set, even if it's in /lib or /usr/lib; so ./configure doesn't > > properly compile and run lame programs unless LD_LIBRARY_PATH is set. > > Something could possibly set this variable in the configure script, > if > > not, then a warning saying to set it would be nice. > > I'll take a deeper look at this. > > > e) I'm not really sure what the story is, but import/nuv doesn't seem > > to compile as it's looking for lzo1x.h, but my version of libavutil > (I > > presume it's the latest) only has lzo.h, and doesn't have the > variable > > names nuv is looking for, I did a --disable-nuv > > The lzo header that nuv module needs it is shipped by (lib)LZO package, > not by ffmpeg! > I didn't explicitly enable nuv or lzo; should it be enabled by default? > Bests, > > -- > Francesco Romani // Ikitt > [ Out of memory. ~ We wish to hold the whole sky, ~ But we never will. > ] >