[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Different compilation based on filename

From: CHEN Cheng
Subject: Re: Different compilation based on filename
Date: Mon, 14 Sep 2009 08:04:00 +0800
User-agent: Mutt/1.5.17 (2007-11-01)

On Sat, Sep 12, 2009 at 06:32:51PM -0400, Paul Smith wrote:
> Another is constructed variable names.  Variable names in make can
> consist of other variables.  So you could do something like this:
>       foo.o_CFLAGS = -g
>       %.o : %.c
>               $(CC) $(CFLAGS) $(address@hidden) -o $@ -c $<
> The $(address@hidden) (or, equivalently, $($(@)_CFLAGS)) expands to the value
> contained in the variable named by concatenating the target ($@) with
> the string _CFLAGS.
> Personally I find this method the most aesthetically pleasing, mainly
> because in my complex make environments I like to have all the "user
> visible" makefile purely data-driven: they simply declare variables but
> never need to declare rules.  The rules are all created in some deeply
> magical common makefiles set up for the project.

Beautiful. It reminds me the Automake style and the Linux kernel Kbuild,
while the Kbuild also put variable (non-automatic) into variable names.

Thanks, Paul, for the nice articles, including the jobserver description.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]