当前位置: 代码迷 >> WinCE >> wince6.0上6410的BSP,"build and sysgen"后报3个异常,求解~(国庆被命令调驱动…帮帮忙…)
  详细解决方案

wince6.0上6410的BSP,"build and sysgen"后报3个异常,求解~(国庆被命令调驱动…帮帮忙…)

热度:145   发布时间:2016-04-28 12:49:51.0
wince6.0下6410的BSP,"build and sysgen"后报3个错误,求解~(国庆被命令调驱动……帮帮忙……)
BLDDEMO: Generating OS Design Folders
Failed to load C:\WINCE600\OSDesigns\S3C6410_DEMO\S3C6410_DEMO

\S3C6410_DEMO.pbxml:

Tools Install Dir in registry is missing.
BLDDEMO: Done Generating OS Design Folders
BLDDEMO: Generating OS Design Files to C:\WINCE600\OSDesigns\S3C6410_DEMO

\S3C6410_DEMO\Wince600\SMDK6410_ARMV4I\oak
Failed to load C:\WINCE600\OSDesigns\S3C6410_DEMO\S3C6410_DEMO

\S3C6410_DEMO.pbxml: 【在输出中找了很久,第一个错误大概是这部分吧……】
……
……
……
……
……
BUILD: [01:0000000475:WARNN ] SsapMp4Parser.def(5) : warning LNK4017: DESCRIPTION statement not supported for the target platform; ignored
BUILD: [00:0000000477:WARNN ] File: C:\WINCE600\platform\SMDK6410\lib\ARMV4I\retail\atapi_common_lib.lib does not exist (2).
BUILD: [00:0000000478:WARNN ] File: C:\WINCE600\platform\SMDK6410\lib\ARMV4I\retail\s3c6410_cf_atapi.lib does not exist (2).
BUILD: [00:0000000479:WARNN ] File: C:\WINCE600\platform\SMDK6410\lib\ARMV4I\retail\s3c6410_spi.lib does not exist (2).
BUILD: [00:0000000484:PROGC ] Building LINK Pass in C:\WINCE600\PLATFORM\SMDK6410\SRC\DRIVERS\shidu\ directory.
BUILD: [01:0000000494:ERRORE] NMAKE : U1073: don't know how to make 'C:

\WINCE600\OSDesigns\S3C6410_DEMO\S3C6410_DEMO\Wince600\SMDK6410_ARMV4I\OSDesigns\S3C6410_DEMO\S3C6410_DEMO\SDKs\SDK1\obj\TE6410'

BUILD: [01:0000000496:ERRORE] NMAKE.EXE TargetExeFiles -i -c BUILDMSG=Stop.BUILDROOT=C:\WINCE600\PLATFORM\SMDK6410 LINKONLY=1 NOPASS0=1MAKEDLL=1 failed - rc = 2
【以上2个错误一直都存在】
……
……
……
Build for Windows CE (Release 601) (Built on Aug 17 2006 15:18:52)
File names: Build.log Build.wrn Build.err Build.dat
Sysgening platform C:\WINCE600\platform\SMDK6410
\WINCE600\build.err

BLDDEMO: There were errors building S3C6410_DEMO

S3C6410_DEMO - 3 error(s), 98 warning(s)
========== 生成: 0 成功或最新,1 失败,0 被跳过 ==========

------解决方案--------------------
打开build.err文件,在里面搜索error,找出具体的错误,贴出来
  相关解决方案