From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-04-28 09:13:34
Vladimir Prus wrote:
> John Maddock wrote:
>>Thanks, it should really mention define/include at the very least, and as
>>I asked before, is there an equivalent to <sysinclude> any more?
> No, because I still don't understand what <sysinclude> does and how it
> differs from <include>. If I'm told, I can add this.
For compilers that care.. <sysinclude> adds a search path when one uses
'#include <somefile.hpp>', and <include> adds a search path when one
uses '#include "somefile.hpp"'. In gcc-tools.jam this is not implemented
by using the builtin system vs. user paths options. But instead by
keeping two separate SYSINCLUDE vs. INCLUDE lists and placing the
SYSINCLUDE before the INCLUDE in the gcc invocation. This is because GCC
has additional semantics it puts on what it has as real sysinclude paths
(like turning off warnings). But in cw-tools.jam it's implemented as two
different options because it handles it "correctly".
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk