[Ffmpeg-devel] GCC 4 Compiler warnings
Sun Jul 31 00:09:17 CEST 2005
So I can spend some time next week looking at GCC4 warnings. What is the
prodedure to submit a patch?
Use diff to generate a patch, and post it to the mailing list, or submit it
to someone on the development team or...
----- Original Message -----
From: "M?ns Rullg?rd" <mru at inprovide.com>
To: "FFMpeg development discussions and patches" <ffmpeg-devel at mplayerhq.hu>
Sent: Saturday, July 30, 2005 7:10 AM
Subject: Re: [Ffmpeg-devel] GCC 4 Compiler warnings
Kent Williams <norman-k-williams at uiowa.edu> writes:
> Hi! I'm new to messing around with ffmpeg, but I have built it and
> have 2 questions
> 1. I've checked out the CVS version, and grabbed the x264 library. I
> built the x264 library, and installed it in a local 'target tree' --
> i.e. x264 is configured with 'configure --prefix=/scratch/opt/video.'
> In most autoconf projects, if you define LDFLAGS before the configure
> you can add -L commands, in this case I'd need
> -L/scratch/opt/video/lib added to the ffpmeg link line before -lx264,
> but the configure/Makefile for ffmpeg ignore LDFLAGS.
> So the question is WHERE is x264 supposed to live surch that ffmpeg
> can link to it?
It can be installed anywhere the linker will look for it. To add more
flags, use configure --extra-ldflags=...
> 2. There are several hundred warnings reported by gcc4. Most of them
> can be silenced with trivial changes that won't affect the code
> generated. Does anyone care about these? Should I try and fix them
> and submit a patch?
Warnings should be silenced, IMHO.
mru at inprovide.com
ffmpeg-devel mailing list
ffmpeg-devel at mplayerhq.hu
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.9.7/60 - Release Date: 7/28/2005
More information about the ffmpeg-devel