Hello. I saw some posts on this list about compiling for Windows CE, but they are a couple years old and were honestly a tad over my head. I also tried posting about this on StackOverflow with no responses. With the last couple releases (1.46 and 1.47) the Boost release notes mentioned that one of the test compilers was "Visual C++, Windows Mobile 5, with STLPort: 9.0," which implies that compiling for Windows CE works fine.

 

Anyway, everything I've found regarding compiling Boost for Windows CE seems to revolve around the file contained here: http://www.boost.org/development/tests/trunk/VeecoFTC.html . However, I'm having trouble understanding how to use it. This is what I've done so far:

 

1. Compile STLPort for Windows CE.

2. Install Boost.Build according to the Getting Started Guide (http://www.boost.org/doc/libs/1_47_0/more/getting_started/windows.html). I'm a little shaky here, since bootstrap.bat seems to be specific to ntx86 and ntx86_64. Have I already screwed up, or is that just referring to the host system?

 

Assuming I've been correct up to this point, I need to run b2 with something along the lines of:

 

b2 -- build-dir=build-directory toolset=toolset-name --build-type=complete stage

 

I assume that the build directory is the prefix I used when installing Boost.Build, and the build type and stage will remain as given, but I'm not certain what toolset name to use. The VeecoFTC file has multiple entries for msvc and stlport, so I removed the entries that DIDN'T contain "wm5." I then run the following command:

 

b2 --build-dir=C:\boost-build toolset=msvc --build-type=complete stage

 

And I get a bunch of errors like:

 

compile-c-c++ C:\boost-build\boost\bin.v2\libs\regex\build\msvc-9.0~wm5~stlport5.2\debug\threading-multi\has_icu_test.obj

The system cannot find the path specified.

 

Indeed, that file not exist, but has_icu_test.obj.rsp DOES exist there. Am I missing something? Am I even on the right track?

 

Thanks for any assistance.

 

Kyle