From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-07-07 00:01:01
[2002-07-06] gclbb-jamboost_at_[hidden] wrote:
>In article <20020706132802-r01010800-a585b50a-0860-0108_at_188.8.131.52>,
>Rene Rivera <jamboost_at_[hidden]> wrote:
>>[2002-07-06] Greg Comeau wrote:
>Now that this is in the right NG, I'll just restate that the
>compiler status info at boost site has reported of Comeau C++
>for LINUX for quite some time now (I believe by Jens).
Now that I've looked at the status stuff :-) There is an easy answer to the
dilema... The regression status pages don't use Boost.Build to compile the
tests. It uses direct commands, as stated in the .../status/compiler.cfg
file. I think some of the regression testing is going to change soon but I
don't know the details there.
>>>* I'm not sure what http://www.boost.org/tools/build/como-tools.html
>>> represents, but suspect that it needs corrections. If somebody
>>> could elaborate what is expected of that URL, I'd be glad to provide
>>> revisions, especially now that new versions of Comeau C++ are more
>>> automated, have new capabilities, etc.
>>It represents what the build system (Boost.Build) currently supports as
>>configuration variables. These are not what the compiler supports, i.e.
>>environment variables. Therefore this would only change if the toolset
>I'm confused then, because como-tools.html says:
> "The como toolset responds to the following variables which
> can be set in the environment"
>and for some others it looks at if is the compilers environment
>variables. If the "como toolset" != "Comeau C++", then what is? :)
Somewhat of a misleading statement :-) The clarification...
"como toolset" == "Boost.Build support for Comeau C++"
The confusing part is that those variables can be set either directly or in
the environment. And even more confusing is that we try and use environment
variables as pre-configured normally by a user of a given toolset.
>>> Also, is this bjam'ing procedure different for different platforms,
>>> or does bjam recognize what platform it is on? (IOWs, invoking
>>> como can be slightly different for different platforms, and so I'm
>>> unclear how that's recognized programmatically, or described in your
>>Right now as far as I can tell the como support is Windows sepcific. Take
>>look at the .../tools/build/como-tools.jam and tell me if that's true...
>>after all you are the expert on Comeau C/C++ ;-)
>I don't know anything about jam, so I'm not able to say if that's
>true or not, especially if the build system supports its own
>environment variables, so I'm not clear on all that's involved.
* I looked at the como toolset a bit more, and it's definately as specific
in support as the description says. It only works in Win32/VC.
* We can tell which platform we are running in, and therefore adjust the
compiler invocations accordingly. But again that's not done in the current
como toolset support.
* I'd be willing to add support for more of the Comeau backends, but I'd
need help in doing so. Specifically I'd need:
1. Documentation for the compiler options based on which backend. I
haven't looked at the documentation you have on the website but hopefully
the info is in there.
2. Someone(s) who is willing to test the new toolset. This someone(s)
would need to know how to access the Boost CVS files. And compile on the
various platforms we want to support.
-- 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