Re: [Boost-build] "p" libraries with STLPORT [WinCE]

Subject: Re: [Boost-build] "p" libraries with STLPORT [WinCE]
From: David Deakins (ddeakins_at_[hidden])
Date: 2009-04-15 10:44:34

Paul Heil wrote:
> I'm compiling Boost 1.38 with STLPort 5.2.1 using Microsoft Visual 
> Studio 9.0 under Windows XP SP3 for Windows Mobile 5 (ARMV4I). 

> 
> My user-config.jam file contains:

>     <compileflags>-DBOOST_PROTO_MAX_ARITY=10
>     <compileflags>-DBOOST_MPL_CFG_NO_PREPROCESSED_HEADERS
>     <compileflags>-DBOOST_MPL_LIMIT_METAFUNCTION_ARITY=10
> 

Paul,

Just for your reference, you don't really need the 3 defines above (not 
that it will hurt anything to have them).  We are doing some special 
stuff with Boost.Proto where we need more than the standard 5 arity so 
we run the regression tests with an arity of 10.  You probably don't 
need this and it might slow down your compile times a bit.

In addition, you should probably be aware that we have slightly modified 
the stock release of STLport 5.2.1 and I haven't yet gotten around to 
documenting our changes (or attempting to submit them for formal 
inclusion in STLport).  I should probably include a little blurb about 
this in our regression test page to avoid confusion.  Beyond some minor 
bug fixes, the main change is that we have supplemented STLport with 
some basic implementations of some of the CRT functions that WinCE is 
missing.  These include time, clock, gmtime, localtime, environ, getenv, 
remove, rename, wctomb, mbtowc, mblen, strerror, strxfrm, wcsxfrm, and 
the errno constants in <errno.h>.  Most of these should only be a 
problem if you are trying to build certain specific libraries.  If you 
run into issues, post what you are seeing and I can try to give you 
pointers in the right direction.

-Dave