Benjamin Kosnik wrote:
For testing outside of the build directory, it would be convenient to
have $SUBJECT.
This could be used in conjunction with -dumpversion to create
on-the-fly include and library directory paths for C++ includes in a
sane manner, much like the following:
Why do you need this? For installed-compiler testing, the compiler
already searches the obvious places. (I'm not trying to be cute: I'm
genuinely curious.)
I agree that it would be nice if -print-search-dirs listed include
directories. It already lists the paths searched for programs and
libraries, so that seems like a logical place to add header directories.
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
