Subject: Re: Per-target specific vars in mk files
To: Luke Mewburn <>
From: Julio M. Merino Vidal <>
List: tech-userlevel
Date: 07/22/2007 12:39:00
On 22/07/2007, at 3:51, Luke Mewburn wrote:

> I added support for COPTS.<name> to <> in rev 1.93  
> (2003/07/22)
> I don't recall why we switched from `_' to `.' as the separator.
> I know that sh(1) variables can't have `.' in them, whereas make(1)
> supports it, so using `.' prevents sh from being used to set
> environment variables that make(1) will inherit.

Good point; I didn't think of that.

>   | If there  isn't, do you think it's worth to sweep these to  
> unify them
>   | all to  use the same separator?
> That would require a rewrite of Makefiles not in the tree
> (i.e used by users / third-parties) that use the existing semantics.
> Besides the asthetics of consistency (which are not a bad thing per  
> se),
> is there any reason to change what we currently have?

Not really.  I was adding some other variables to the files and  
wondered why there was such discrepancy between names.

Julio M. Merino Vidal <>