CPPPATH not in man page

[bdbaddog]

This issue was originally created at: 2001-12-14 15:59:08.
This issue was reported by: stevenknight.
stevenknight said at 2001-12-14 15:59:08

From Stephen Kennedy:

I ran into a few gotchas when trying it on some of our
projects:
(is the sourceforge bug tracker being used? there were
zero bugs entered)

• if the include path is set through CXXFLAGS instead
  of
  CPPPATH (not in the man page!) then dependency
  generation
  silently fails. (i.e. foo.o only depends on foo.cpp)

steve9000 said at 2001-12-14 17:25:17

Also perhaps it should be an error for an include switch
to be specified in CXXFLAGS.

I'd suggest that all variables which are created from
other variables have some kind of checking to ensure
that each part comes from the correct source.

stevenknight said at 2001-12-16 20:31:42

Steve9000--

The problem I see with trying to warn about this is that
whether or not a given flag should come from one variable or
another depends on the compiler being used. Complaining
about someone specifying '-Ifoo' in CXXFLAGS isn't
Builder-specific, it's specific to that fact that the $CXX
variable happens to be 'gcc'. Someone using Microsoft VC++
would have to have a different check.

I agree that warnings would be useful, though, so I'm going
to add a TODO item to track whether or not we can think of
some way to generalize this. If you have any suggestions,
I'm all ears.

issues@scons said at 2001-12-16 20:31:42

Converted from SourceForge tracker item 493515

gregnoel said at 2008-03-18 03:51:23

Change anthonyroach to aroach. Are you still out there?

gregnoel said at 2008-03-18 04:59:28

Gack! Changing the name shouldn't have changed the status!

gregnoel said at 2008-03-18 05:05:26

Gack! Changing the name shouldn't have changed the status!