none
Failure in Building Windows CE Compact 7 - OS Design RRS feed

  • Question

  • I am facing difficulties building an OS Design for the eBox 3310 device. I get the following errors.. when I try to get a Build done..

     

    Error 1 Error(s) in directory "C:\WINCE700\platform\common\src\common\cache\". C:\WINCE700\build.log 17848

    Error 2 NMAKE : fatal error U1077: 'C:\WinAVR-20090313\utils\bin\type.EXE' : return code '0x35' C:\WINCE700\build.log 17849

    Error 3 TargetCompilePass  -nologo BUILDMSG=Stop.  BUILDROOT=C:\WINCE700\platform\common NOLINK=1 NOPASS0=1 failed - rc = 2. C:\WINCE700\build.log 17851

    Error 4 BLDDEMO: ERROR: There were errors building CEBASE. C:\WINCE700\build.log 17881

    Friday, March 18, 2011 8:40 PM

All replies

  • Can you show us the lines of build.log indicated in above message?

    Friday, March 18, 2011 8:46 PM
  • Here's the build.log text associated with the errors. Thanks!
    BUILD: [02:0000000241:ERRORE] Error(s) in directory "C:\WINCE700\platform\common\src\common\io\base\".
    BUILD: [02:0000000242:ERRORE] NMAKE : fatal error U1077: 'C:\WinAVR-20090313\utils\bin\type.EXE' : return code '0x35'
    BUILD: [02:0000000243:INFO  ] Stop.
    BUILD: [02:0000000244:ERRORE] TargetCompilePass  -nologo BUILDMSG=Stop.  BUILDROOT=C:\WINCE700\platform\common NOLINK=1 NOPASS0=1 failed - rc = 2.
    BUILD: [00:0000000245:PROGC ]                        Files  Warnings  Errors
    BUILD: [00:0000000246:PROGC ] Midl                       0         0       0
    BUILD: [00:0000000247:PROGC ] Message                    0         0       0
    BUILD: [00:0000000248:PROGC ] Precomp Header             0         0       0
    BUILD: [00:0000000249:PROGC ] Resource                   0         0       0
    BUILD: [00:0000000250:PROGC ] XRPack                     0         0       0
    BUILD: [00:0000000251:PROGC ] MASM                       0         0       0
    BUILD: [00:0000000252:PROGC ] SHASM                      0         0       0
    BUILD: [00:0000000253:PROGC ] ARMASM                     0         0       0
    BUILD: [00:0000000254:PROGC ] MIPSASM                    0         0       0
    BUILD: [00:0000000255:PROGC ] C++                        0         0       0
    BUILD: [00:0000000256:PROGC ] C                          0         0       1
    BUILD: [00:0000000257:PROGC ] CheckLibs                  0         0       0
    BUILD: [00:0000000258:PROGC ] Static Libraries           0         0       0
    BUILD: [00:0000000259:PROGC ] Exe's                      0         0       0
    BUILD: [00:0000000260:PROGC ] Dll's                      0         0       0
    BUILD: [00:0000000261:PROGC ] Preprocess deffile         0         0       0
    BUILD: [00:0000000262:PROGC ] Resx                       0         0       0
    BUILD: [00:0000000263:PROGC ] CSharp Compile             0         0       0
    BUILD: [00:0000000264:PROGC ] VCProj Compile             0         0       0
    BUILD: [00:0000000265:PROGC ] Other                      0         0       1
    BUILD: [00:0000000266:PROGC ] 
    BUILD: [00:0000000267:PROGC ] Total                      0         0       2
    BUILD: [00:0000000268:PROGC ] 
    BUILD: [00:0000000269:PROGC ] 0 Warnings,  2 Errors
    BUILD: [00:0000000270:PROGC ] GetSystemTimes (seconds): Idle: 6     Kernel: 11    User: 13   
    BUILD: [00:0000000271:PROGC ] Elapsed  time  (seconds): 12   
    CEBUILD: BUILDMSG: There were errors building. Check C:\WINCE700\build.err
    BLDDEMO: ERROR: There were errors building CEBASE.
    Saturday, March 19, 2011 7:34 AM
  • Try removing C:\WinAVR-20090313\utils\bin from PATH. Actually you should clean up your PATH variable altogether. Different toolchains tend to screw up eachother, this doesn't happen with Windows CE only. I've seen similar stuff happening with something as simple as an echo command.

    • Proposed as answer by Kartoffelsalat Saturday, March 19, 2011 3:33 PM
    Saturday, March 19, 2011 3:33 PM
  • Try removing C:\WinAVR-20090313\utils\bin from PATH. Actually you should clean up your PATH variable altogether. Different toolchains tend to screw up eachother, this doesn't happen with Windows CE only. I've seen similar stuff happening with something as simple as an echo command.

    Thanks Kartoffelsalat.. I'm a total newbie, how shall I clean the PATH? I'm using VS2008 With the necessary Platform Builder and SDKs installed.
    Saturday, March 19, 2011 4:42 PM
  • I tried to clear the PATH through VS2008 Command prompt

     

    set PATH = 

     

    That sets it to null... 

    Still doesn't work. The NMAKE still gives an error with C:\WinAVR-20090313\utils\bin which is a DIR completely unassociated with this project.


    Sunday, March 20, 2011 5:48 PM
  • Could you be more specific about what you did?   "I tried to clear the PATH through VS2008 Command prompt" is a little vague.  The fact that you are still able to build at all suggests that whatever you did had no effect.
    Bruce Eitman (eMVP)
    Senior Engineer
    Bruce.Eitman AT Eurotech DOT com
    My BLOG http://geekswithblogs.net/bruceeitman

    Eurotech Inc.
    www.Eurotech.com
    Sunday, March 20, 2011 7:38 PM
    Moderator
  • Wouldn't it be necessary to clear the PATH env variable before launching VS at all?  I can't say for certain, but it seems that VS would inherit the existing env variables and then add to them.  You could certainly get away with clearing out the "master" PATH variable via Windows.

    To accomplish that, setting or clearing the env variables is a little different for each flavor of Windows.  Google "set environment variables" for details that apply to your situation.  Be cautious about it, as that may break some other tools or apps that you use if you just clear PATH for use within VS.


    email me: D HART (remove the space after the D) AT OICO dot COM
    Tuesday, March 22, 2011 6:52 PM
  • I am seeing this same issue. Did you ever find out how to fix this?
    Friday, June 10, 2011 2:15 AM
  • Yes I did.. I deleted the C:\WinAVR-20090313\utils\bin mentioned in the error Or u'd like to rename it. This folder was not related to the installation and was for the ARV boards we use.

     

    Anyways, the previous installation messed up the PATH variable i assume. But renaming/deleting it worked well.

    Friday, June 10, 2011 4:21 PM