RE: [jamboost] Re: More toolset thoughts

From: Mark Elston (m.elston_at_[hidden])
Date: 2004-06-15 14:30:00

BTW,

Where is the documentation for how to specify the 'using ...' lines?
It came as a surprise that there were differences, or even multiple
parameters, or that they could be different for different compilers.

Oh, wait. I think I see it in the tools/xxx.jam in the rule init (...).
Is that it?

Mark

> -----Original Message-----
> From: Vladimir Prus [mailto:ghost_at_[hidden]]On Behalf Of Vladimir
> Prus
> Sent: Tuesday, June 15, 2004 12:27 AM
> To: jamboost_at_[hidden]
> Subject: Re: [jamboost] Re: More toolset thoughts
> 
> 
> David Abrahams wrote:
> 
> > > Some other require to pass "installation root", e.g.
> > >
> > > using msvc : : P:\.....\vc98 ;
> >
> > That's just the equivalent of path for that compiler. I see that
> > toolset as needing resources (including the compiler executable) in
> > multiple subdirectories of that installation directory.
> 
> Right, but that's still not the path to compiler itself. The 
> problem is that 
> it is non-intuitive which path should be used:
> 
> P:\.....\vc98\bin
> P:\.....\vc98\
> P:\....Microsoft Visual Studio
> 
> > > 1. Gcc is changed to match other compilers.
> >
> > Yes.
> 
> Ok. 
> 
> > > 2. All toolset accept name of the compiler, and not some installation
> > > root. This would make it simple to explain how toolset is to be
> > > initialized.
> >
> > How will the directory for a nonstandard installation be 
> specified, then?
> 
> For vc, we'd strip the compiler name and "bin" directory from the 
> compiler 
> path passed to the init rule. After that, the initialization will 
> proceed as 
> now. This assumes that the last directory name is called "bin", 
> but we assume 
> that anyway.
> 
> - Volodya
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 
>