From: Matthew L. <ml...@le...> - 2005-01-14 21:25:13
|
Gehua and Marc, I've installed avifile as a Debian package and also built it from source. In both cases the header files where put into an avifile-0.7 directory. In the case of the Debian package they went into /usr/include/avifile-0.7. My guess is that older versions of avifile use an include/avifile directory and then they changed it for some reason in the latest version 0.7. My solution was to create a symbolic link from /usr/include/avifile to /usr/include/avifile-0.7, but I'm sure there must be a better way. -Matt Leotta On Fri, 2005-01-14 at 09:01 -0800, Marc Anderson wrote: > Gehua > > Gehua, > Files put into /usr/local/include is not the system > default header files. So the files you've mentioned > (avifile-0.7) may be installed by the guys after the > system installation. And there is no such files in my > box. > > Marc. > > Just a side comment: > I tried to compile vidl on a Linux platform. The > systemwise avifile headers > are resided in /usr/local/include/avifile-0.7. But > vidl/vidl_avifile_avicodec.h is trying to include > <avifile/avifile.h>, which > cannot be found. > > The avifile was compiled directly from 0.7 snapshot. > Maybe the > AVIFILE_INCLUDE_DIR should be the whole string and > vidl_avifile_avicodec.h > should include only <avifile.h>. Or the headers files > should always be put > into a folder named "avifile"? > > Comments? > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - now with 250MB free storage. Learn more. > http://info.mail.yahoo.com/mail_250 > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Vxl-users mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-users |