WinCE : What does mean the error: U1073: don't know how to make

2
votes

After trying to build a WinCE OS image for ARM V4 I encountered the following error

NMAKE : fatal error U1073: don't know how to make 'C:\WINCE600\public\common\oak\lib\ARMV4I\retail\lmemhs.lib'

Then I decided to run an Advanced Command "Rebuild Current BSP and Subprojects" and I found next error.

BUILD: [01:0000002558:ERRORE] NMAKE : U1073: don't know how to make 'C:\WINCE600\OSDesigns\PENTA_ARM_PC\PENTA_ARM_PC\Wince600\SMDKC100_ARMV4I\cesysgen\oak\lib\ARMV4I\retail\gpe.lib' BUILD: [01:0000002560:ERRORE] NMAKE.EXE TargetLibFiles -i -c BUILDMSG=Stop. BUILDROOT=C:\WINCE600\PLATFORM\SMDKC100 CLEANBUILD=1 LINKONLY=1 NOPASS0=1 failed - rc = 2

What does this mean ? Why these files are missing? Are they part of the Win CE or the ARM BSP ? I am using Win CE 6.0 Trial.

2
compiler-errorsbuild-processwindows-ce
Since GPE stands for Graphics Primitive Engine I would say that your BSP has a problem and is not building properly. Did you do a sysgen before building your BSP? – yms
Yes I did with the same problem. I suppose the problem is in the lmemhs.lib file. I am not sure but, when I installed the WinCE development environment the installer asked me if I want to work with ARM or x86. My previous project was intended for x86 so I installed x86. My current project is for ARM. I suppose that lmemhs.lib is something related to memory management that should be different on ARM. Maybe I am wrong but it looks like that is the problem. I do not understand why MS took this approach. – Patrik

2 Answers

1
votes

Since GPE stands for Graphics Primitive Engine I would say that your BSP is encountering a problem and is not building properly.

You mentioned in comments that you did not install ARM support on your development environment, and you also said that your target system is an ARM device. It turns out that you cannot build an ARM platform if you do not install ARM support on your development environment.

It seems you will have to re-install (or install in another system) your development environment with ARM support, and apply a sysgen operation on your solution.

0
votes

I had the same problem.

it's probably due the fact that you installed the x86 rollup update (only) but not the arm4i rollup. this file is updated/added by wince r3 rollup

https://www.microsoft.com/en-us/download/details.aspx?id=36505

choose the arm4i download