Re: include path problems, or cons vs. make incompatability?

[Brian O'Keefe]

Thanks Steven. I thought my CPPPATH was defined properly:

CPPPATH        => "$INCLUDE -I/home/okeefe/src/dirA",

But just for kicks, I changed it to this:

CPPPATH        => '/home/okeefe/src/dirA',

and now it works for me :)

The reason I didn't do this originally was to also have the $INCLUDE from 
my Construct file included in the inc search path. So, I just switched the 
order of these two as follows:

CPPPATH        => "/home/okeefe/src/dirA -I$INCLUDE",

and it works also. Interesting why the order matters for these, but this 
solves my problem. Thanks a lot!

At 04:35 PM 2/23/2001, Steven Knight wrote:
> You need to specify CPPPATH in the construction environment to tell Cons
> which directories to search and, by extension, what -I options to add to
> compile lines.  If you haven't done this, then Cons isn't set up to
> do what you want.
>
> The other thing that occurs to me is whether gcc knows how to expand
> the '~' in your '-I~/src/dirA' argument above.  Unless I'm really out
> of date, no shell that I know of will reach in and expand a ~ inside an
> argument like that.  Cons certainly won't.  I bet it's getting passed
> through to gcc, and I doubt that gcc handles that expansion, either.
> You might have better luck explicitly using $ENV{HOME} instead of '~' in
> your Construct/Conscript files.


Brian O'Keefe
Spinnaker Networks
address@hidden