Re: cant compile in osx

(Quoting painstakingly reordered for my sanity's sake. Please don't
top-post.)

James Barros wrote:

> On Feb 23, 2006, at 9:52 AM, James Barros wrote:
>
> > On Feb 18, 2006, at 7:29 AM, herve.flores wrote:

> > Oddly enough, I can ./compile; make; sudo make install for faac
> > alone fine. it's getting ffmpeg with the --enable-faac option to
> > compile that isn't working.
> >
> > Thanks for the tip though :)
>
> Ok, so grabbed todays cvs, and getting a different error now.
>
> cc -O3 -g -Wall -Wno-switch -DHAVE_LRINTF -no-cpp-precomp -pipe 
> -fomit-frame-pointer -force_cpusubtype_ALL -Wno-sign-compare -faltivec 
> -mdynamic-no-pic -DHAVE_AV_CONFIG_H -I.. -I/Users/james/sw/ffmpeg/ libavutil 
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -c -o xvidff.o xvidff.c
>
> xvidff.c:26:18: error: xvid.h: No such file or directory
>
> and then a host of issues spawn from that. Can I just copy the xvid.h
> file from the xvid_core package at xvid.org into my libavcodec
> directory and expect this to build? or is that a completely different
> file?

Neither of the above. You need to install the XviD development files,
including both the header and the libraries; they do not belong in your
libavcodec directory, but in your system include and library paths
(probably /usr/local/include and /usr/local/lib).

Alternately, just drop '--enable-xvid' from your configure options;
libavcodec's own internal MPEG-4 codec is generally quite sufficient,
and there is little advantage to stacking XviD's implementation on top
of that. (I do it myself, of course, but then I'm a ludicrous
completist.)

--
      The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.