Re: where does the lame lib go to be included in ffmpeg configure

Paul Buelow wrote:

> > This isn't documented because it's very generic; the process of
> > installing libraries and headers is not specific to LAME, it is
> > pretty much the same across all different libraries you're likely
> > to think of. It is assumed that anyone knowledgeable enough to get
> > and compile the CVS of a project is going to either know the basics
> > of this sort of thing already or have the intestinal fortitude to
> > figure it out for themselves.
>
> Apparently the prefix path was not happy. Copying the files to
> /usr/lib and /usr/include solved it.

Yes, installed libraries must be in installed locations - not just in
some random spot on your system. Note that there is a conceptual
difference between '/usr/local/lib' and '/usr/lib', in terms of what
libraries should be in which location, although I've never been entirely
clear on precisely what that difference is; I would have expected LAME
to go under /usr/local/, but it was not placed there on my system.

In any case, libraries you compile yourself should almost certainly
always go under /usr/local/lib (and headers under /usr/local/include)
rather than just under /usr/lib. It's not going to be fatal if you don't
change it, but that is still proper practice.

> > > Do you cvs like this below or is there another place for lame dev
> > > files that I need to compile ffmpeg with lame?
> > > cvs -d:pserver:anonymous@xxxxxxxxxxxxxxxxxxx:/cvsroot/lame login
> > > cvs -d:pserver:anonymous@xxxxxxxxxxxxxxxxxxx:/cvsroot/lame checkout -P lame
> >
> > I honestly don't know (I don't run LAME from CVS), and I don't
> > think I'm interested enough to dig the information out - especially
> > not given how slow sourceforge tends to be. Unless you have some
> > specific reason to be running the latest, most bleeding-edge
> > version, you should probably install your distro's LAME development
> > package, rather than downloading, compiling and installing the CVS
> > version of LAME before trying to compile FFmpeg.
>
> No I don't want/need the latest though cvs of the latest is required
> to post issues here.

CVS of LAME is not required for FFmpeg bug reports; CVS of FFmpeg is all
that is needed. As long as the other libraries are detected and compile
correctly with the CVS version of FFmpeg, we almost certainly don't care
which versions you're running.

--
      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.