Re: [jamboost] msvc-tools.jam question

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-07-18 16:24:34

----- Original Message -----
From: "Beman Dawes" <bdawes_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Thursday, July 18, 2002 4:10 PM
Subject: [jamboost] msvc-tools.jam question

> In typical toolsets like metrowerks, the C++ compile actions are named
like
> this:
>
> #### C++ ####
> rule C++-action
> {
> ...
> }
>
> actions metrowerks-C++-action
> {
> ...
> }
>
> But in the msvc toolset, the naming is like this:
>
> #### C++ ####
> rule C++-action
> {
> ...
> }
>
> actions vc-C++
> {
> ...
> }
>
> It there a reason for that?

Yes. VC is being used to refer to the general protocol being used by a
whole host of toolsets which exted this one: como, intel-win32,
msvc-stlport, ...

> OK if I change the actions name to:
>
> actions msvc-C++-action
>
> So that log analysis tools don't have to special case that compiler?

It won't help because all those toolsets use the same actions. Your log
analysis should not rely on the action name for anything.

P.S. I've often said that trying to postprocess the results of the build
process with an external tool is not likely to work well, and I think you
are running into many of the problems I was thinking of. It is possible to
assemble the .html/XML/whatever from the build results within the build
system, and I think it would be easier. However, the test system
requirements still need to be understood first...

-Dave