From: David Abrahams (dave_at_[hidden])
Date: 2003-11-04 14:43:46
Vladimir Prus <ghost_at_[hidden]> writes:
> David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> >> Well, it's augmenting the list of directories that will be stuck into
>> >> PATH before the executable is run. The reason for adding
>> >> $(CYGWIN_ROOT)/$(p) is that if the developer of the Jamfile was using
>> >> Cygwin bjam, the absolute path "/foo/bar" actually maps to
>> >> "$(CYGWIN_ROOT)/foo/bar" for the person running the tests under
>> >> regular windows bjam.
>> > I'm afraid I don't understand this. Most of the the time 'p' is
>> > implicitly generated by Boost.Build, so under regular windows bjam it
>> > will still be correct. nt
>> I guess it's for "the rest of the time".
> And what is that time?
Sorry, I'm not sure.
> I can imagine only one case: when user explicitly sets gRUN_PATH, or
> something like that, in the command line or in environment. Was that
> the motivation?
I'm afraid I don't remember.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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