Re: [jamboost] Comments on new gcc-nocygwin-tools.jam?

From: William E. Kempf (wekempf_at_[hidden])
Date: 2003-01-22 02:22:44

Raoul Gough said:
> I've come up with a new gcc-nocygwin-tools.jam, which contains only the
> following code:
>
> extends-toolset gcc ;
> CFLAGS += -mno-cygwin ;
> C++FLAGS += -mno-cygwin ;
> LINKFLAGS += -mno-cygwin ;
>
> This requires an up-to-date gcc-tools.jam (since 2003/01/17) and an
> up-to-date Cygwin gcc installation (support was added around October
> 2002, according to my information). I've posted the new documentation at
> http://home.clara.net/raoulgough/boost/gcc-nocygwin-tools.html

Great!

> Contrary to my initial reckoning, using gcc-tools.jam and setting
> <cxxflags> on the command line does *not* work correctly, because it
> confuses python.jam into thinking it has a Cygwin Python installation
> (you need a Windows native Python for use with -mno-cygwin).
>
> There seem to be some problems with building the Boost test libraries,
> both with gcc-nocygwin and native mingw. See the attached traces for
> details. I guess these problems are caused by differences between Unix
> and Windows shared library linkage styles, but I haven't really
> investigated (seems like it was already broken, since the mingw
> toolset has exactly the same problems).

Hmmm... I didn't have any troubles at all. I replaced the content of
gcc-nocygwin-tools.jam with what you have above, and ran "bjam
-sTOOLS=gcc-nocygwin test" in the $BOOST/libs/thread/test directory, which
built all of the Boost.Threads and Boost.Test libraries, as well as the
test harness for Boost.Threads, and ran the resulting executables. 
Everything worked fine (minus a couple of runtime bugs found for this
"new" toolset in the Boost.Threads library). This was all done on a
recently updated CVS repository.

> If there are no objections, I'll check the new nocygwin support into CVS
> at the end of the week.

Well, other than addressing Dave's concerns about older Cygwin GCC
installations, I have no objections and am anxiously awaiting the new
toolset!

William E. Kempf
wekempf_at_[hidden]