Re: [jamboost] Re: Toolset init changes: gcc, intel and sun

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-06-23 02:45:46

Christopher Currie wrote:
> Vladimir Prus wrote:
> > I've just made another round of simplifying toolset initialization, and
> > touched gcc, intel and sun. The changes are:

> This is a welcome change and improvement, thanks for making it so clean!
> This now allows me a configuration I've always wanted, which is the
> ability to support the Purify tool as a version of the compiler:
>
> using sun : purify : "purify CC" ;
>
> allows me to use "bjam sun-purify" as an alternate toolset. Great work!

Cool. I wonder, though, if the above "using" syntax gives you a warning that 
compiler is not found? Of course, that's only a warning, but would be nice to 
kill it.

> > And finally a question. Does anybody object if I really switch all the
> > other toolsets to use command name as opposed to "root directory"? I.e.
> >
> > using borland : : H:\CBuilderX ;
> >
> > will become
> >
> > using borland : : H:\CBuilderX\bin\bcc32.exe ;
> >
> > This syntax is more verbose, but it can be uniform for all toolsets -- so
> > users don't have to remember which toolsets needs a full path, and which
> > a path to 'installation root'.
>
> I think this is an excellent idea. Being able to specify the executable
> explicity is what allows me the above, 

I'm afraid for msvc, which need to find a path to "setup script", it would be 
hard to prepend arguments like "purify", at least for now.

> and I think there should be a 
> consistent initialization for all toolsets.

That's for sure. Let me pick the next victim... that's going to be borland 
toolset.

- Volodya