[FFmpeg-devel] [PATCH] Support building dependency files with non-GCC compilers

Diego 'Flameeyes' Pettenò flameeyes
Thu Oct 2 19:17:32 CEST 2008


M?ns Rullg?rd <mans at mansr.com> writes:

> Why did you move this block?

Because the point where DEPEND_CMD was set before was before $cc was
set.

> Do the Intel and Sun compilers produce correct output?

I do think so, it seems to work fine; there is one quirk with Sun Studio
compiler (it will ignore files in /usr/include but will keep on
explicitly depending on its includes in /opt; I'll report it as a bug to
them), but it's not like GCC/ICC are much better (they still report any
file in /usr/include if the path was included with -I rather than
-isystem, and almost nothing uses -isystem).

> Setting the command to "false" is a bit harsh, since it makes building
> with any other compiler impossible.

This is probably true, I guess I'm a bit harsh myself ;) Should I change
it to true so that dependency information is just ignored when the
compiler is not known?

> I'm still in favour of always using gcc.  It has quirks aplenty, but
> there will be no new surprises.

I've thought quickly about this but there is at least one problem:
CFLAGS. The flags that will be used for Sun Studio or ICC might not work
with GCC, and I wouldn't be surprised if GCC would then fail to properly
generate the dependencies. I suppose it's a bet on what is most likely,
I guess.

-- 
Diego "Flameeyes" Petten?
http://blog.flameeyes.eu/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20081002/db562333/attachment.pgp>



More information about the ffmpeg-devel mailing list