不知道什么原因啊，郁闷！
build.log中的内容如下：
Build Log
--------------------Configuration: Samsung smdk2440: ARMV4I_Debug--------------------
Starting Build: blddemo
==============
FILESYS_COMPONENTS=fsheap fsmain fsreg fsysram fsreplbit fsdbase fspass fsadvertise msgqueue
DEVICE_COMPONENTS= devcore iorm pmif
PM_COMPONENTS= pm_default_pdd pm_mdd pm_pdd_common
GWE1_COMPONENTS=wmbase gweshare gwesmain immthunk msgque GSetWinLong CePtr foregnd idle kbdui uibase msgbeep audio
GWE2_COMPONENTS=mgbase mgbitmap mgblt mgblt2 mgdc mgdibsec mgdraw mgrgn mgwinmgr tchui calibrui mggradfill mgalphablendstub mgtt mgdrwtxt mgpal mgpalnat
GWE3_COMPONENTS=accel btnctl caret cascade imectl clipbd cmbctl defwndproc dlgmgr dlgmnem edctl gcache gwectrl icon iconcmn imgctl lbctl loadbmp loadimg menu menuscrl mOverlap MouseAndTouchCursor iconcurs mcursor mcursor8 cursor cursor8 mNoTapUI
GWE4_COMPONENTS=nclient oom sbcmn scbctl startup stcctl winmgr startui oomui sbcmnview nclientview gcacheview btnctlview stcctlview cmbctlview lbctlview msgbox msgbox_hpc dlgmgr_hpc menu_hpc EditControlOs timer column atom drawmbar hotkey syscolor mgdx mgalias journal mgtci
DCOM_MODULES= ole32 oleaut32 uuid
OLE32_COMPONENTS=mcombase mcommem mcomstr mcommon mcomlib ole232 docfile msf exp mcomstm
GDIEX_MODULES= imaging
IMAGING_COMPONENTS= img_png img_libpng img_pngdecoder img_gif img_liblzw img_gifdecoder img_jpeg img_jpegfull img_jpegmem img_jpegdecoder img_bmp img_bmpdecoder
IE_MODULES= shdoclc shdocvw inetcpl urlmon wininet shlwapi uuid ieceext mlang
SCRIPT_MODULES= jscript
SERVERS_MODULES= timesvc
SHELLSDK_MODULES= aygshell
SHELL_MODULES= explorer shcore ceshell qvgap
CESHELL_COMPONENTS= ceshapi ceshui taskbarlist
SHCORE_COMPONENTS= shcore path
WCESHELLFE_MODULES= htmlview peghelp browser iexplore webview msscript control ctlpnl cplmain AdvBacklight connpnl intlp
DATASYNC_MODULES= cefobj repllog rapisrv eventrst rra_stm systemcpl udp2tcp wceload unload
NETCF_MODULES= dotnet
Sysgening platform E:\WINCE500\platform\smdk2440
Sysgening platform E:\WINCE500\platform\smdk2440
\WINCE500\build.err
E:\WINCE500\build.err
E:\WINCE500\build.log
E:\WINCE500\build.wrn
已复制 3 个文件。
BLDDEMO: There were errors building YC2440
Results
YC2440 - 0 error(s), 5 warning(s)
16 个解决方案
#1
E:\WINCE500\build.err
里面有什么？
里面有什么？
#2
builderr里面为E:\WINCE500\build.log(1) : error SYSGEN0000: error(s) in sysgen phase
不知道写的什么意思
#3
同一个环境下在Release下定制内核正常，生成的有NK.bin和NK.nb0，但为什么在调试DEBUG下就不行了？？生成不了?
#4
求指教啊！！！
#5
把DEBUG目录下的全部文件删除，然后进行一次SYSGEN
#6
谢谢，我试一下
#7
解决了吗，分享一下。
#8
原厂BSP的问题.
我们的原厂文档上写, 建议用 release.
我们的原厂文档上写, 建议用 release.
#9
竟然可以这样呢？
#10
用5楼的方法，居然还出现错误了，郁闷！难道是BSP的原因
#11
建议但也没一定要用release啊,各种不懂啊！！
#12
Romimage.exe 是根据Ce.bib来包含什么文件进NK的，不能生成NK，很大原因是Romimage.exe的问题，看看你的PB是不是过期了，或者少了Romimage.exe文件。
个人理解，希望对你有用
个人理解，希望对你有用
#13
贴一段帮助文档的解释：
Romimage.exe is a locator application that creates Windows CE binary image (.bin) files, usually limited to a single file called Nk.bin. This means that Romimage performs the following actions:
Reads Ce.bib to determine which %_FLATRELEASEDIR% binaries and files to include in the final run-time image.
Assigns physical memory addresses to these binaries and files.
Creates the run-time image Nk.bin.
The Make Binary Image tool (Makeimg.exe) calls a number of programs and batch files in the process of making the run-time image.
Makeimg.exe performs all processing in the %_FLATRELEASEDIR% directory. After processing, the Ce.bib file defines which binaries and files are to be included in the run-time image. By default, the run-time image is named Nk.bin.
If you have modified and built files in your OS design, you can copy these files to %_FLATRELEASEDIR% and then run the Make Binary Image tool to include these files in the run-time image. This can decrease time spent running builds on your entire OS design. For more information about adding files to the run-time image, see Adding a File to a Run-time Image.
Makeimg.exe calls the following programs:
The NLS Compression tool (Cenlscmp.exe) enables national language support (NLS) compression. Cenlscmp.exe combines the settings file Nlscfg.out and the input file Nlssrc.txt to build the output file Wince.nls in the %_FLATRELEASEDIR% directory.
The File Merge tool (Fmerge.exe) merges settings files to create four initialization files, which are created in the %_FLATRELEASEDIR% directory. Fmerge.exe also includes settings files from dependent projects — for example, the Wceshell or Wceshellfe project.
If the settings files for the dependent projects are defined in the _DEPTREES environment variable, and if they also exist in the %_FLATRELEASEDIR% directory, Fmerge.exe merges them into the appropriate initialization file.
The following table shows the original files and merged initialization file for each file type.
Original files Merged initialization file
Common.bib, Config.bib, Project.bib, Platform.bib Ce.bib, which identifies all the Windows CE files to be combined into the run-time image.
Common.reg, Project.reg, Platform.reg Reginit.ini, which provides a collection of registry entries for the run-time image.
Common.dat, Project.dat, Platform.dat Initobj.dat, which provides a description of the directory and file locations for the run-time image.
Common.db, Project.db, Platform.db Initdb.ini, which defines the creation of any databases in the Windows CE object store.
The Registry Compression tool (Regcomp.exe) performs registry compression by reading Reginit.ini and compressing it into a binary registry file called Default.fdf, which is eventually included in the run-time image. Default.fdf is always loaded on a cold boot. The Ce.bib file references Default.fdf, which then initializes the system registry on the target device.
The Resource Update tool (Res2exe.exe) replaces the resources in specified .dll, .exe, or Control Panel (.cpl) files with the appropriate resources for the language specified by the LOCALE environment variable.
The Text to Unicode tool (Txt2ucde.exe) converts any ASCII text strings in Initobj.tmp, which was created by Fmerge.exe, to Unicode text strings and creates the file Initobj.dat, which contains the Unicode conversion.
The ROM Image Builder tool (Romimage.exe) reads the Ce.bib file to determine which binaries and files, located in %_FLATRELEASEDIR%, are to be included in the run-time image, including how they are stored in memory.
The Ce.bib file also lists the following processed files: Wince.nls, Reginit.ini, Initobj.dat, Initdb.ini, and Default.fdf.
Then, Romimage.exe combines the binaries and files into the run-time image, which is usually called Nk.bin unless specified otherwise in the MEMORY section of the Ce.bib file
Romimage.exe is a locator application that creates Windows CE binary image (.bin) files, usually limited to a single file called Nk.bin. This means that Romimage performs the following actions:
Reads Ce.bib to determine which %_FLATRELEASEDIR% binaries and files to include in the final run-time image.
Assigns physical memory addresses to these binaries and files.
Creates the run-time image Nk.bin.
The Make Binary Image tool (Makeimg.exe) calls a number of programs and batch files in the process of making the run-time image.
Makeimg.exe performs all processing in the %_FLATRELEASEDIR% directory. After processing, the Ce.bib file defines which binaries and files are to be included in the run-time image. By default, the run-time image is named Nk.bin.
If you have modified and built files in your OS design, you can copy these files to %_FLATRELEASEDIR% and then run the Make Binary Image tool to include these files in the run-time image. This can decrease time spent running builds on your entire OS design. For more information about adding files to the run-time image, see Adding a File to a Run-time Image.
Makeimg.exe calls the following programs:
The NLS Compression tool (Cenlscmp.exe) enables national language support (NLS) compression. Cenlscmp.exe combines the settings file Nlscfg.out and the input file Nlssrc.txt to build the output file Wince.nls in the %_FLATRELEASEDIR% directory.
The File Merge tool (Fmerge.exe) merges settings files to create four initialization files, which are created in the %_FLATRELEASEDIR% directory. Fmerge.exe also includes settings files from dependent projects — for example, the Wceshell or Wceshellfe project.
If the settings files for the dependent projects are defined in the _DEPTREES environment variable, and if they also exist in the %_FLATRELEASEDIR% directory, Fmerge.exe merges them into the appropriate initialization file.
The following table shows the original files and merged initialization file for each file type.
Original files Merged initialization file
Common.bib, Config.bib, Project.bib, Platform.bib Ce.bib, which identifies all the Windows CE files to be combined into the run-time image.
Common.reg, Project.reg, Platform.reg Reginit.ini, which provides a collection of registry entries for the run-time image.
Common.dat, Project.dat, Platform.dat Initobj.dat, which provides a description of the directory and file locations for the run-time image.
Common.db, Project.db, Platform.db Initdb.ini, which defines the creation of any databases in the Windows CE object store.
The Registry Compression tool (Regcomp.exe) performs registry compression by reading Reginit.ini and compressing it into a binary registry file called Default.fdf, which is eventually included in the run-time image. Default.fdf is always loaded on a cold boot. The Ce.bib file references Default.fdf, which then initializes the system registry on the target device.
The Resource Update tool (Res2exe.exe) replaces the resources in specified .dll, .exe, or Control Panel (.cpl) files with the appropriate resources for the language specified by the LOCALE environment variable.
The Text to Unicode tool (Txt2ucde.exe) converts any ASCII text strings in Initobj.tmp, which was created by Fmerge.exe, to Unicode text strings and creates the file Initobj.dat, which contains the Unicode conversion.
The ROM Image Builder tool (Romimage.exe) reads the Ce.bib file to determine which binaries and files, located in %_FLATRELEASEDIR%, are to be included in the run-time image, including how they are stored in memory.
The Ce.bib file also lists the following processed files: Wince.nls, Reginit.ini, Initobj.dat, Initdb.ini, and Default.fdf.
Then, Romimage.exe combines the binaries and files into the run-time image, which is usually called Nk.bin unless specified otherwise in the MEMORY section of the Ce.bib file
#14
PB过期了可能性不大，Romimage.exe也存在...bin\i386中，谢谢指教！
#15
既然如此 clone一个relaese BSP？？试试
#16
菜鸟级别，还望指教具体操作！
#1
E:\WINCE500\build.err
里面有什么？
里面有什么？
#2
builderr里面为E:\WINCE500\build.log(1) : error SYSGEN0000: error(s) in sysgen phase
不知道写的什么意思
#3
同一个环境下在Release下定制内核正常，生成的有NK.bin和NK.nb0，但为什么在调试DEBUG下就不行了？？生成不了?
#4
求指教啊！！！
#5
把DEBUG目录下的全部文件删除，然后进行一次SYSGEN
#6
谢谢，我试一下
#7
解决了吗，分享一下。
#8
原厂BSP的问题.
我们的原厂文档上写, 建议用 release.
我们的原厂文档上写, 建议用 release.
#9
竟然可以这样呢？
#10
用5楼的方法，居然还出现错误了，郁闷！难道是BSP的原因
#11
建议但也没一定要用release啊,各种不懂啊！！
#12
Romimage.exe 是根据Ce.bib来包含什么文件进NK的，不能生成NK，很大原因是Romimage.exe的问题，看看你的PB是不是过期了，或者少了Romimage.exe文件。
个人理解，希望对你有用
个人理解，希望对你有用
#13
贴一段帮助文档的解释：
Romimage.exe is a locator application that creates Windows CE binary image (.bin) files, usually limited to a single file called Nk.bin. This means that Romimage performs the following actions:
Reads Ce.bib to determine which %_FLATRELEASEDIR% binaries and files to include in the final run-time image.
Assigns physical memory addresses to these binaries and files.
Creates the run-time image Nk.bin.
The Make Binary Image tool (Makeimg.exe) calls a number of programs and batch files in the process of making the run-time image.
Makeimg.exe performs all processing in the %_FLATRELEASEDIR% directory. After processing, the Ce.bib file defines which binaries and files are to be included in the run-time image. By default, the run-time image is named Nk.bin.
If you have modified and built files in your OS design, you can copy these files to %_FLATRELEASEDIR% and then run the Make Binary Image tool to include these files in the run-time image. This can decrease time spent running builds on your entire OS design. For more information about adding files to the run-time image, see Adding a File to a Run-time Image.
Makeimg.exe calls the following programs:
The NLS Compression tool (Cenlscmp.exe) enables national language support (NLS) compression. Cenlscmp.exe combines the settings file Nlscfg.out and the input file Nlssrc.txt to build the output file Wince.nls in the %_FLATRELEASEDIR% directory.
The File Merge tool (Fmerge.exe) merges settings files to create four initialization files, which are created in the %_FLATRELEASEDIR% directory. Fmerge.exe also includes settings files from dependent projects — for example, the Wceshell or Wceshellfe project.
If the settings files for the dependent projects are defined in the _DEPTREES environment variable, and if they also exist in the %_FLATRELEASEDIR% directory, Fmerge.exe merges them into the appropriate initialization file.
The following table shows the original files and merged initialization file for each file type.
Original files Merged initialization file
Common.bib, Config.bib, Project.bib, Platform.bib Ce.bib, which identifies all the Windows CE files to be combined into the run-time image.
Common.reg, Project.reg, Platform.reg Reginit.ini, which provides a collection of registry entries for the run-time image.
Common.dat, Project.dat, Platform.dat Initobj.dat, which provides a description of the directory and file locations for the run-time image.
Common.db, Project.db, Platform.db Initdb.ini, which defines the creation of any databases in the Windows CE object store.
The Registry Compression tool (Regcomp.exe) performs registry compression by reading Reginit.ini and compressing it into a binary registry file called Default.fdf, which is eventually included in the run-time image. Default.fdf is always loaded on a cold boot. The Ce.bib file references Default.fdf, which then initializes the system registry on the target device.
The Resource Update tool (Res2exe.exe) replaces the resources in specified .dll, .exe, or Control Panel (.cpl) files with the appropriate resources for the language specified by the LOCALE environment variable.
The Text to Unicode tool (Txt2ucde.exe) converts any ASCII text strings in Initobj.tmp, which was created by Fmerge.exe, to Unicode text strings and creates the file Initobj.dat, which contains the Unicode conversion.
The ROM Image Builder tool (Romimage.exe) reads the Ce.bib file to determine which binaries and files, located in %_FLATRELEASEDIR%, are to be included in the run-time image, including how they are stored in memory.
The Ce.bib file also lists the following processed files: Wince.nls, Reginit.ini, Initobj.dat, Initdb.ini, and Default.fdf.
Then, Romimage.exe combines the binaries and files into the run-time image, which is usually called Nk.bin unless specified otherwise in the MEMORY section of the Ce.bib file
Romimage.exe is a locator application that creates Windows CE binary image (.bin) files, usually limited to a single file called Nk.bin. This means that Romimage performs the following actions:
Reads Ce.bib to determine which %_FLATRELEASEDIR% binaries and files to include in the final run-time image.
Assigns physical memory addresses to these binaries and files.
Creates the run-time image Nk.bin.
The Make Binary Image tool (Makeimg.exe) calls a number of programs and batch files in the process of making the run-time image.
Makeimg.exe performs all processing in the %_FLATRELEASEDIR% directory. After processing, the Ce.bib file defines which binaries and files are to be included in the run-time image. By default, the run-time image is named Nk.bin.
If you have modified and built files in your OS design, you can copy these files to %_FLATRELEASEDIR% and then run the Make Binary Image tool to include these files in the run-time image. This can decrease time spent running builds on your entire OS design. For more information about adding files to the run-time image, see Adding a File to a Run-time Image.
Makeimg.exe calls the following programs:
The NLS Compression tool (Cenlscmp.exe) enables national language support (NLS) compression. Cenlscmp.exe combines the settings file Nlscfg.out and the input file Nlssrc.txt to build the output file Wince.nls in the %_FLATRELEASEDIR% directory.
The File Merge tool (Fmerge.exe) merges settings files to create four initialization files, which are created in the %_FLATRELEASEDIR% directory. Fmerge.exe also includes settings files from dependent projects — for example, the Wceshell or Wceshellfe project.
If the settings files for the dependent projects are defined in the _DEPTREES environment variable, and if they also exist in the %_FLATRELEASEDIR% directory, Fmerge.exe merges them into the appropriate initialization file.
The following table shows the original files and merged initialization file for each file type.
Original files Merged initialization file
Common.bib, Config.bib, Project.bib, Platform.bib Ce.bib, which identifies all the Windows CE files to be combined into the run-time image.
Common.reg, Project.reg, Platform.reg Reginit.ini, which provides a collection of registry entries for the run-time image.
Common.dat, Project.dat, Platform.dat Initobj.dat, which provides a description of the directory and file locations for the run-time image.
Common.db, Project.db, Platform.db Initdb.ini, which defines the creation of any databases in the Windows CE object store.
The Registry Compression tool (Regcomp.exe) performs registry compression by reading Reginit.ini and compressing it into a binary registry file called Default.fdf, which is eventually included in the run-time image. Default.fdf is always loaded on a cold boot. The Ce.bib file references Default.fdf, which then initializes the system registry on the target device.
The Resource Update tool (Res2exe.exe) replaces the resources in specified .dll, .exe, or Control Panel (.cpl) files with the appropriate resources for the language specified by the LOCALE environment variable.
The Text to Unicode tool (Txt2ucde.exe) converts any ASCII text strings in Initobj.tmp, which was created by Fmerge.exe, to Unicode text strings and creates the file Initobj.dat, which contains the Unicode conversion.
The ROM Image Builder tool (Romimage.exe) reads the Ce.bib file to determine which binaries and files, located in %_FLATRELEASEDIR%, are to be included in the run-time image, including how they are stored in memory.
The Ce.bib file also lists the following processed files: Wince.nls, Reginit.ini, Initobj.dat, Initdb.ini, and Default.fdf.
Then, Romimage.exe combines the binaries and files into the run-time image, which is usually called Nk.bin unless specified otherwise in the MEMORY section of the Ce.bib file
#14
PB过期了可能性不大，Romimage.exe也存在...bin\i386中，谢谢指教！
#15
既然如此 clone一个relaese BSP？？试试
#16
菜鸟级别，还望指教具体操作！