David Abrahams wrote:
>>> using msvc : 8.0 ;
....
>>> Both with and without cl in the path.
>> ......
>>> command = [
common.get-invocation-command msvc : cl.exe :
>>> $(command)
>>> : [ 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.
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.
> 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.
>>> In any case, even when I passed
>>> "c:\Program Files (x86)\Microsoft Visual
Studio 8\VC\BIN\amd64\cl"
>>> as the command parameter, there was trouble.
Because I wasn't
>>> explicitly passing <setup> through my
"using" command, it once again
>>> couldn't get into the block where the
setup-option was set to
>>> x86_amd64.
>>
>> Do you have a binary called
>>
>> "c:\Program Files (x86)\Microsoft Visual
Studio 8\VC\BIN\cl.exe"
>>
>> Can you list all binaries called "cl.exe"
in your VCBIN directory?
>
> I'm not near my machine right now and it's not
convenient for me.
> IIRC you have access to that machine and can look
yourself.
Ok, I'll try to check.
- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
