|
Boost-Build : |
From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-11-06 17:19:15
[2002-11-06] David Abrahams wrote:
>Rene Rivera <grafik666_at_[hidden]> writes:
>
>> >Also, I see that paths for toolsets are hardcoded. Can we do better?
>> >Will building work if I have "bcc32" in path, but it's installed in
>> nonstandard
>> >location. (Well I can check this at home, but later).
>>
>> I did what I knew how to do. Ideally on Windows doing things like reading
>> the registry would be the ticket. But I don't know how to do that from a
>> script. But yes we can do better, even if it's just testing various
common
>> install locations, as the MSVC check does.
>
>Well, checking the PATH should be fairly easy, since it gets imported
>into the global module and we have the GLOB rule.
Yes, but again your thinking in Jam terms ;-) It's the BAT file that's doing
the detection. But I think I can come up with a way to check the PATH for
executables in the BAT.
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]
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