From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2007-01-12 15:26:57
I have a macro that I need to define in the project requirements for
a number of toolsets (darwin, gcc, intel, pgi, pathscale, sgi, sun)
but I need to suppress the macro definition for only one toolset
Is there a clean way of doing this rather than the brute force
approach? I tried this syntax to tell bjam to ignore the macro on
vacpp and on all other platforms define it, but this doesn't work.
Is the brute force solution (listing each <toolset> explicitly) the
only approach? I have a lot of macros that behave like this,
undefined on some toolsets, defined on others.
-- Noel Belcourt
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