[coyotos-dev] Building coyotos (missing inttypes.h?)

[Tom Bachmann]

Jonathan S. Shapiro wrote:
> On Wed, 2006-01-18 at 18:25 +0100, Bas Wijnen wrote:
> 
> 
>>You want to avoid the variable completely?
> 
> 
> I want to ensure that the user does not have to set ANY environment
> variables unless they are in a very unusual case. We will not achieve
> this, but this is the goal.
> 

This is a nice goals, but usually _all_ projects have some kind of 
configuration step (sometimes explicit, sometimes more implicit). I also 
work on projects without an explicit configure step, but experience 
showed me that saving some variables in a file is useful.
Examples:

In a private scons project, I save the variables given once on command 
line in a file called config.cache, so I don't have to set them always.

In another make only (well, it's bsd make) project I'm involved in we 
use a $TOPLEVEL/user.mk to allow the user to set variables like 
U_CFLAGS, U_GCC etc.

Maybye you should consider this, as I do not think you can make the 
process magically work for everyone but nonetheless should make it a 
little bit comfortable for those with "unusual situations".

> The code you wrote requires a shell script, and is therefore not a
> feasible solution. We need something that does the job within make.
> 
> A solution has already been sent to the list.
> 
> 
> shap
> 
-- 
-ness-