On Tue, Mar 18, 2008 at 11:19:17PM +0100, Francesco Romani wrote:
> 
> On Tue, 2008-03-18 at 21:53 +0100, Francesco Romani wrote:
> 
> > > I downloaded the latest snapshot from
> > > http://ffmpeg.mplayerhq.hu/ffmpeg-export-snapshot.tar.bz2 onto a machine
> > > that never had ffmpeg on it before.  It appears to me that that's an
> > > official source of the latest build.  It doesn't seem to put much in the
> > > ffmpeg directory.
> > 
> > You're right, my ffmpeg installation is out of date. I'll update our
> > build system and codebase ASAP.
> 
> This issue deserves more resources. I've added an issue report here:
> http://tcfoundry.hostme.it/mantis/view.php?id=61
> 
> looks like DV fixes (mantis issue #0000051) and this one are the new
> hotspots and blockers for the new release cycle (1.1.0beta1 and
> 1.0.6rc2).
> I'm in doubt for HEAD. HEAD isn't intended for distro's packaging so we
> can theoricalluy simplify things without worrying; on the other hand, I
> don't want to mantain yet another different version of configure script,
> so I'll likely adopt unified changes in order to minimize the
> maintenance burden.
> 
> We can just look for ffmpeg headers in new locations and forget the rest
> since AFAIK debian and ubuntu are stuck on old layout and I don't want
> to lose compatibility with those.

it should be possible to just remove the ffmpeg/ part from the #include
lines.  `pkg-config --cflags libavcodec libavutil` should give
the correct CFLAGS for both old and new versions of ffmpeg.

-- 
[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org

Reply via email to