Re: [boost] Contributing new toolset support

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-02 06:28:36

----- Original Message -----
From: "Raoul Gough" <RaoulGough_at_[hidden]>

> I'd like to contribute support for a new build toolset for boost, but
I'm
> not sure how to go about it.
>
> Details: using the -mno-cygwin option it is possible to use the gcc
from
> cygwin to produce native windows executables and dll's (like mingw
does).

Yep, I've tried it.

> Turning on this option also means providing a replacement standard
library,
> in my case STLport,

Hmm, I didn't know that. Why won't the usual one work?

> and seems to make building a working boost jam pretty
> difficult.

You don't need to rebuild jam for every compiler you want to use it
with...

> I think the best way to go is to introduce a new toolset name
> (e.g. NOCYGWIN) which does all the necessary stuff.

I'm reluctant to make changes to Boost.Build v1, but a new toolset
doesn't seem like a big problem. However, I hope you are using the
"extends-toolset" rule as with gcc-stlport-tools.jam.

> Actually, I've had the
> build working for a few days, but it would need some tidying up for
general
> use.
>
> Is there sufficient interest to include this in the CVS? How would I
go
> about contributing the necessary changes?

Post them to the jamboost list (www.yahoogroups.com/messages/jamboost);
we'll look them over.

Thanks,
Dave