Re: If I want registry files will be vaild after I modify registry files (eg. platform.reg), must I rebuild the ce project?
- From: "Henrik Viklund" <henrik.viklund@xxxxxxxxx>
- Date: 20 Jun 2006 03:44:13 -0700
If you change one of the "major" reg/bib/dat/db files such as
platform.reg or project.reg from the parameter's view, you can manually
copy these files into the flat release directory instead of going
through a full sysgen.
To further ease the need to manually copy files or doing sysgen:s you
can use "#include" statements:
IF MYCATALOGITEM
#include
"$(_winceroot)\platform\MyBSP\SRC\DRIVERS\MyDirver\myDriverRreg.reg"
ENDIF MYCATALOGITEM
If you break down, for example, your platform.reg or project.reg file
using "#include" statements you can keep changes, and thus the need to
copy project.reg to the flat release directory to a minimum.
Henrik Viklund
http://www.addlogic.se
PowerAll wrote:
If I want registry files will be vaild after I modify registry files
(eg. platform.reg), must I rebuild the ce project?
.
- References:
- Prev by Date: Re: Error in Sysgen: res2res / cefilter / U1077
- Next by Date: Re: using net command with XP shared folder. Strange TCP/IP behavior.
- Previous by thread: If I want registry files will be vaild after I modify registry files (eg. platform.reg), must I rebuild the ce project?
- Next by thread: Can't Get The Correct ActiveConfig in USB driver
- Index(es):
Relevant Pages
|
