David Deakins wrote:
>
> In order to get the console tests to link properly for WinCE, some
> additional machinery is required. You want the link command line to
> include the additional /entry:mainACRTStartup option to say that it
> should look for main and not WinMain as the entry point. I do this with
> the following statement at the end of my user-config.jam:
>
> project
> : requirements
> <toolset>msvc-9.0~wm5~stlport5.2,<user-interface>console:<linkflags>/entry:mainACRTStartup
>
> ;
>
> -Dave
>
Thanks, that worked!
The build runs to completion, and tries to execute the resulting exes,
which fails, since they are Windows CE exes. I think the other lines in
VeecoFTC's user-config.jam somehow plug the WM5TestLauncher into the
boost test infrastructure so that it downloads the exes to an actual CE
device (or maybe an emulator).
I manually copied the files to my emulator and called CreateProcess on
them. That fails with GetLastError 126, "The specified module could not
be found". "dumpbin /imports system_error_test.exe" shows that
system_error_test.exe links to msvcr80d.dll. Do you know of a way to fix
this?
Andy
_______________________________________________
Unsubscribe & other changes:
http://lists.boost.org/mailman/listinfo.cgi/boost-build
