> -----Original Message----- > From: Jacob Meuser [mailto:[EMAIL PROTECTED] > Sent: Monday, March 17, 2008 6:22 PM > To: 'transcode Developers Mailing List' > Subject: Re: [transcode-devel] Compilation issues with plugins > > On Mon, Mar 17, 2008 at 05:26:35PM -0400, Jacob (Jack) Gryn wrote: > > Hi, > > > > > > > > It seems there are a few things that may complicate compilation; that > could > > probably be simplified; figured I'd share my issues, hopefully to > simplify > > things in the future, or at the very least, help others in the future > hack > > things to compile. I tried 1.0.5, and then went to the latest cvs > version. > > > > > > > > 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) > > > > run configure like so: > > $ env CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" > ./configure > > or LDFLAGS="-L/usr/local/include -L/usr/lib64" if that's how your > system > is set up.
I got it working using the with-module-include and -with-module-lib flags, the issue is to assist the default behaviour to make it easier to compile. > > > 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 bet this is not a problem if you use my first suggestion. Actually, no, as the export_mov.c file is looking for <file.h> when it should be looking for <lqt/file.h> since quicktime puts things in /usr/local/include/lqt/*.h > > -- > [EMAIL PROTECTED] > SDF Public Access UNIX System - http://sdf.lonestar.org >
