[FFmpeg-devel] [PATCH] C99ify array initialisation in mxfdec.c
Wed Jul 21 02:36:02 CEST 2010
On Tue, Jul 20, 2010 at 4:04 AM, Axel Holzinger <aholzinger at gmx.de> wrote:
> On Mon, Jul 19, 2010 at 5:48 PM, Ramiro Polla wrote:
>> On Mon, Jul 19, 2010 at 6:14 AM, Axel Holzinger
>> <aholzinger at gmx.de> wrote:
>> > Sure, it's Intel's C compiler for Windows icl, 11.1 065.
>> Does FFmpeg finally compile with icl? (I haven't tested in a
> Not really. As you already know in the past I tried to use icl with
> the FFmpeg configure script directly, but I'm not good enough in
> scripting to be able to add native icl support. That's a pitty,
> because I think that would be the most straight solution and I think
> it is possible. I know that it takes some additions (like stdint.h,
> etc.), but most things come with MinGW and some parts could be hosted
> on svn.ffmpeg.org as SVN externals.
> As Intel's compiler under Linux (icc) tries to behave like gcc (and
> use/accept gcc switches) and under Windows (icl) tries to imitate
> Microsoft's compiler. That's the reason that you can't easily use icl
> to build FFmpeg.
> What I'm trying out now is to sort of translate icc's Linux switches
> to icl's Windows switches. The problem is that there are many switches
> that don't have a counter part on the other side, so I guess full
> featured build will not be possible/easy. Also I haven't yet thought
> about asm.
There is a tool called wgcc that claims to translate the command line
switches, you could try that. FFmpeg's configure also has a section of
command line mapping (look for "if $cc -v 2>&1 | grep -qi ^gcc;
then") that could be used. We're collecting info about icl here:
http://wiki.multimedia.cx/index.php?title=Icc#Windows_version . If you
have more information it'd be nice to have it updated.
More information about the ffmpeg-devel