> 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.)
This is needed if you need to find the C++ includes, but are not using
the C++ compiler.
> I agree that it would be nice if -print
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
> but in the meantime, I'm wondering if there is a much easier way to go
> about this that I'm currently overlooking.
...instead I will rip off comp_base_dir from libgloss.exp.
-benjamin
