Subject: Re: [Boost-build] How to stop propagate include paths of internal library
From: Phillip Seaver (phil_at_[hidden])
Date: 2009-03-09 11:08:22
> Phillip Seaver <phil <at> apago.com> writes:
>> I describe how I do it here:
> Thanks for the link, this helps. It would be nice, if I wouldn't need to patch
> the boost-build rules.
I would prefer that the distribution had it, too, but at least it's a
very small, self-contained patch, rather than several files.
>> I prefer it that way to avoid header conflicts between third-party
>> libraries and reduce my search path. I don't recall whether I ran into
>> the command-line limitation, but I wouldn't now, since the msvc toolset
>> uses "response files" to reduce the command-line size.
> "Unfortunately" I use gcc and I have not found out how to pass gcc the arguments
> via a file instead of specifying everything on the command line.
At the bottom of this page --
-- they have an "@file" option like in msvc. I would assume it got
added in the first release 4.2, but I don't really want to go digging
around in the gcc repository to figure it out. :-) I didn't see it in
the gcc 4.1 documentation or any of the earlier releases I looked at.
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