Re: [jamboost] creating dll file is not availab;e on v2 mingw boost1.31

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-07-06 08:50:42

shelarcy wrote:

> > I'm afraid it's hard to ask gcc to tell if it's mingw or not. The only
> > solution I see is to tell we're using mingw on initialization time,
> > something
> > like:
> >
> > using gcc : 3.3 : : mingw ;
> >
> > I think "mingw" should even should not be a subfeature, just a flag to
> > toolset. Thoughts?
>
> I wrote this code in project-root.jam, but error is also appear.
> I mistook that, or v2 has a problem on mingw?

Sorry for confusion. What I exactly mean is: we really don't work on mingw. 
This is really bad, we used to work there, but a change intended to make 
gcc.jam work on Solaris broken mingw, which I did not notice :-(

So, I really wonder if we should have a mechanism to tell which gcc variant is 
being used -- cygwin, mingw, solaris, or somethng else.

But first of all, I really don't understand why mingw does not work. I've just 
checked, and the linker seems to accept "-h soname" command line option. Do 
you have an idea what's going on?

- Volodya