Re: clean build question

Tech-Archive recommends: Speed Up your PC by fixing your registry

For your convenience I wrote a blog item about cloning the public code: http://guruce.com/blogpost/cloningpubliccodeanexample

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Michel Verhagen (eMVP) wrote:
You should never change anything in the PUBLIC tree. Clone it to your BSP or OSDesign (as a subproject).

Did you read this? http://guruce.com/blogpost/whattobuildwhen
You can find a short example on how to clone in this post: http://guruce.com/blogpost/sdmmcandwindowsce

Also Bruce has a couple of posts about cloning (http://geekswithblogs.net/BruceEitman/Default.aspx)

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Joe Welfeld wrote:
Hi,

I tried the suggestion below and It didn't quite have the results I was expecting. Let's say I modified a file in Public/common/oak/drivers/touch to add a retail message, (not too modify code but I needed to just add one retail message to see some behavior), I was expecting to see in the drivers/touch/obj/x86 directory debug, release, and after sysgening with the changes suggested below, a new obj directory called shipbuild but I do not see shipbuild so the flatrelease directory shipbuild contains the same lib as the release build and my Retailmsg is still printed out. Even when I go to the directory view and re-build with clean I do not get a shipbuild directory under the drivers obj so this doesnt really address my problem ?

Thanks,

Joe W.




"Michel Verhagen (eMVP)" <michel@xxxxxxxxxx> wrote in message news:uujA$BkLJHA.5692@xxxxxxxxxxxxxxxxxxxxxxx
What I always do is create a separate configuration for Debug, Retail and Shipbuild. The "Clean" option only cleans out the release directory (your _FLATRELEASEDIR), it doesn't clean out your BSP obj folders, so when the build system passes over the BSP it sees the files didn't change since last build so it doesn't rebuild. If you change configuration it WILL rebuild (if it's the first time you build a shipbuild) because then the build files will go into a separate folder (like \debug \release \shipbuild).

In PB for CE 5.0, go to menu "Build OS", choose "Configurations...", click on the "Release" configuration, click "Add", replace the configuration name part "Release" to "Shipbuild" and copy settings from your release configuration. Then select this new configuration in the configuration dropdown and go to build settings for this config. Then disable KITL and the Kernel Debugger and enable Shipbuild.


Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Joe Welfeld wrote:
Hello,

I have been building a release build without shipbuild set and I decided to build a ship build to turn off my retail messages. I went to settings and set shipbuild then under build OS tab I checked clean before building and I did a sysgen. I found that many of my RETAIL messages where still there and when I looked at dates of OBJ files I could see they were not re-built even though I selected Clean, I read I am not supposed to do a Build and Sysgen (and I never do) but why does clean not clean everything ? in particular I see obj files under driver directories that have not been re-build. If I go to file view and build individual drivers with the clean set that works ? Can someone explain this behavior, and let me know what I need to do to insure a clean re-builds everything ?


Thanks,

Joe Welfeld


.

Relevant Pages

  • Re: clean build question
    ... Let's say I modified a file in Public/common/oak/drivers/touch to add a retail message,, I was expecting to see in the drivers/touch/obj/x86 directory debug, release, and after sysgening with the changes suggested below, a new obj directory called shipbuild but I do not see shipbuild so the flatrelease directory shipbuild contains the same lib as the release build and my Retailmsg is still printed out. ... Even when I go to the directory view and re-build with clean I do not get a shipbuild directory under the drivers obj so this doesnt really address my problem? ... In PB for CE 5.0, go to menu "Build OS", choose "Configurations...", click on the "Release" configuration, click "Add", replace the configuration name part "Release" to "Shipbuild" and copy settings from your release configuration. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: clean build question
    ... What I always do is create a separate configuration for Debug, Retail and Shipbuild. ... The "Clean" option only cleans out the release directory, it doesn't clean out your BSP obj folders, so when the build system passes over the BSP it sees the files didn't change since last build so it doesn't rebuild. ... I have been building a release build without shipbuild set and I decided to build a ship build to turn off my retail messages. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: clean build question
    ... to add a retail message, (not too modify code but I needed to just add one ... but I do not see shipbuild so the flatrelease directory shipbuild contains ... The "Clean" option only cleans out the release directory (your ... If you change configuration it WILL ...
    (microsoft.public.windowsce.platbuilder)
  • Re: acpi
    ... Once you get the kernel source unpacked, ... > make clean ... > make modules install ... copy over appropriate configuration file to .config ...
    (RedHat)
  • Re: xp fails to start completely
    ... I tried to go into safe mode by hitting f8> at ... Craig - It's kind of hard to troubleshoot this without being able to see ... try Last Known Good Configuration from the same menu as ... If that doesn't do it, then slave the drive in another XP or Win2k or Vista computer, copy the important data and then do a clean install. ...
    (microsoft.public.windowsxp.general)