Boost logo

Boost-Build :

Subject: Re: [Boost-build] [wince] Building Boost for Windows CE... some progress and problems...
From: Andy Schweitzer (a.schweitzer.grps_at_[hidden])
Date: 2009-06-16 09:38:56

Juergen Hunold wrote:
> Hi Andy,
> On Monday 15 June 2009, Andy Schweitzer wrote:
>> Andy Schweitzer wrote:
>> \debug\asynch-exceptions-on\link-static\stdlib-stlport-5.2~evc8~arm\^
>> threading-multi\error_code_test.exe
>> stlportstld.5.2.lib(stlportstld.5.2.dll) : fatal error LNK1112: ^
>> module machine type 'X86' conflicts with target machine type 'THUMB'
> Are you sure that you really have a cross build of STlport ? This
> message indicates that the STLport dll is x86 instead of THUMB.
> and please post the complete linker command line next time.

link command is:
link /NOLOGO /INCREMENTAL:NO /DEBUG /subsystem:console
/LIBPATH:"C:\nan\stl\STLport-5.2.1\lib\vc9" /subsystem:windowsce,5.01
/machine:THUMB /NODEFAULTLIB:oldnames.lib /NODEFAULTLIB:libc.lib
/STACK:262144,4096 coredll.lib corelibc.lib ole32.lib oleaut32.lib
uuid.lib commctrl.lib /VERBOSE:LIB

user-config.jam says:
using stlport : 5.2.1 : "C:/nan/stl/STLport-5.2.1" :
                 "C:/nan/stl/STLport-5.2.1/lib/vc9" ;
using stlport : 5.2~evc8~arm :
                 C:/nan/stl/STLport-5.2.1/stlport :
                 C:/nan/stl/STLport-5.2.1/lib/evc8-arm ;

bjam command line says ... stdlib=stlport-5.2~evc8~arm
... but bjam seems to be picking up the first one, which is in fact X86.
This doesn't happen for bjam of system lib itself but it does for
system\test. Is this intentional? Does the test jamefile need to be
explicitly extended to support other toolsets?

Commenting out the stlport statement makes it pick up the second one...
but then that fails to link to WinMain. In fact it just has main, not
WinMain. it seems like other extensions might be necessary to make the
test work in CE. Is this a known issue?

> Yours,
> Jürgen

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at