[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CPPASCOMPILE doesn't use $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES)
From: |
Thomas Schwinge |
Subject: |
Re: CPPASCOMPILE doesn't use $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) |
Date: |
Wed, 11 Oct 2006 22:02:09 +0200 |
User-agent: |
Mutt/1.5.6+20040907i |
Hello!
On Wed, Oct 11, 2006 at 10:12:33AM +0200, Ralf Corsepius wrote:
> with automake-cvs/HEAD, and using *.S, CPPASCOMPILE doesn't apply
> $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) to its compilation rules.
It also doesn't for 1.9.6, by the way.
> From a Makefile.in:
> CPPASCOMPILE = $(CCAS) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CCASFLAGS) \
> $(CCASFLAGS)
>
> IMO, as *.S sources are supposed to be preprocessed, it would be better
> to let CPPASCOMPILE be processed the same way *.c sources are, i.e. to
> apply "$(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES)":
>
> C-COMPILE from a Makefile.in:
> COMPILE = $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) \
> $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS)
Like you suggest, I would also expect for `COMPILE' and `CPPASCOMPILE' to
behave the same apart from the obvious differences. But those
differences should not include what `COMPILE' and `CPPASCOMPILE' have in
common: the preprocessing. And all of the missing bits are pre processor
flags.
> IMO, though this would introduce an inconsistency to *.s
> (non-preprocessed asm sources) this probably would help users to be
> facing inconsistencies between *.S and *.c/*.cc/*.f etc. languages
> (which use $(DEFS) etc.).
I think I don't understand that part.
Regards,
Thomas
signature.asc
Description: Digital signature