|
Boost : |
From: Robert Ramey (ramey_at_[hidden])
Date: 2005-01-05 22:47:16
Very helpful.
Is there any chance you can upload the test results to the test matrix?
Robert Ramey
Simon Barner wrote:
> Hello Boosters,
> This disables the build of the wchar version of the serialization
> library on this platform. I simply couldn't get it to work, AFAIK libc
> is not ready for wide characters on this platform.
>
> --- libs/serialization/build/Jamfile.orig Mon Dec 13 18:36:52 2004
> +++ libs/serialization/build/Jamfile Mon Dec 13 18:37:28 2004
> @@ -90,12 +90,10 @@
>
> install serialization lib :
> <lib>boost_serialization
> - <lib>boost_wserialization
> ;
>
> stage stage/lib :
> <lib>boost_serialization
> - <lib>boost_wserialization
> :
> <locate>$(BOOST_ROOT)
> common-stage-tag
>
The serialization library consists of 2 libraries: serialization and
wserialization. wserialization implements those facilities which depend on
wide characters. The failure of wserialization to built for lack of wide
character support does not inhibit the usage of the library where wide
characters are not needed.
It turns out that there are number of libraries/compiler combinations which
fail to support wide characters or have some problem with them. In these
cases the wserialization library will fail to build and the corresponding
tests fail to run for lack of a library. So this change should be
unnecessary. Furthermore , there are combination which might miight work -
for example gcc 3.42(or 2.85) + STLPort so the Jamfile should be left to
permit these to be run and tested.
To summarize, the jamfile should be set up to permit an attempt to build
both libraries. If wserialization fails to build, it indicates that that
part of the library cannot be used. However, there's no reason the rest
can' t be used and tested.
Robert Ramey
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk