From: David Abrahams (dave_at_[hidden])
Date: 2007-07-31 11:11:44
on Sun Jul 29 2007, Vladimir Prus <ghost-AT-cs.msu.su> wrote:
> David Abrahams wrote:
>>>> using msvc : 8.0 ;
>>>> Both with and without cl in the path.
>>>> command = [ common.get-invocation-command msvc : cl.exe :
>>>> : [ default-paths $(version) ] : $(version) ] ;
>>> It is highly unlikely for this to return nothing if cl.exe in in PATH.
>>> Are you sure that's the case?
>> No, it's not... and why should it be?
> Because in the part quoted above you've said you have tried with cl
> in the PATH. If that were the case, then 'get-invocation-command'
> is supposed to return something, which you claim it isn't.
Well, frankly, as I said, it's been 7 months, and any untested claims I made
in the past couple of weeks are just "from memory."
> So, I'm trying to figure if get-invocation-command is broken in
> as-yet-unknown way, or you claim that cl.exe is in PATH is wrong.
Regardless, the toolset should work whether or not cl is in the PATH.
>> The registry knows where VS is
>> installed and IIRC our toolset tries to use that information.
> I'm trying to investigate your claim that get-invocation-command returns
> nothing. The fact that registry auto-detection failed to work is independent.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.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