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

[Gary Oberbrunner]

Of course, CPPPATH can now also be an array ref, on any system type.

  CPPPATH => [ $INCLUDE, "/home/okeefe/src/dirA" ],

I don't think this is documented (at least not in 2.2).


 > -----Original Message-----
 > From: address@hidden [mailto:address@hidden
 > Behalf Of Steven Knight
 > Sent: Friday, February 23, 2001 5:15 PM
 > To: Brian O'Keefe
 > Cc: cons-discuss
 > Subject: Re: include path problems, or cons vs. make incompatability?
 > 
 > 
 > On Fri, 23 Feb 2001, Brian O'Keefe wrote:
 > > Thanks Steven. I thought my CPPPATH was defined properly:
 > > 
 > > CPPPATH        => "$INCLUDE -I/home/okeefe/src/dirA",
 > 
 > No, that's not defining CPPPATH properly.  CPPPATH is a colon-separated
 > (semi-colon on Windows NT) path of include directories that Cons will
 > search for #include files *and* turn into -I options for you.

. . . . . . . . . . . . . . . . . . . . . . . . .
Gary Oberbrunner                address@hidden
GenArts, Inc.                   Tel: 617-492-2888
8 Clinton Street                Fax: 617-492-2852
Cambridge, MA 02139 USA         http://web.genarts.com