Re: [Q] How to speed up build process
From: Brian Kuebert (bkuebert_at_xtremex3.com)
Date: 11/12/04
- Next message: Christopher Le [MS]: "Re: PB5.0 SDK build issue"
- Previous message: smiller: "10ms IST latency"
- In reply to: Chuck Zalinski: "RE: [Q] How to speed up build process"
- Next in thread: Dean Ramsier: "Re: [Q] How to speed up build process"
- Reply: Dean Ramsier: "Re: [Q] How to speed up build process"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Nov 2004 15:59:19 -0500
Thanks for the reply Chuck! After reading this I have a question, though:
is setting WINCEREL=1 equivalent to running buildrel after build?
Using WINCEREL=1 then the process would be (from a directory in the PUBLIC
tree):
build
makeimg
but this would be equivalent to WINCEREL not set and doing:
build
buildrel
makeimg
Just trying to make sure I actually understand what you wrote. :-)
Thanks......
-Brian
"Chuck Zalinski" <charlz@online.microsoft.com> wrote in message
news:5ns1ddPyEHA.1884@cpmsftngxa10.phx.gbl...
> The batch file "blddemo" does a lot of things to build a final image. It
> also has a number of shortcuts to speed things up.
>
> Simplified overview of what blddemo does
> * SYSGEN Phase
> This phase builds the CE kernel based on your selected SYSGEN variables
> and
> BSP variables
> - Build anything in Private if needed
> - Build everything in Public
> - Build your BSP under the Platform directory
>
> * Buildrel Phase
> - Copies your built files to the _FLATRELEASEDIR
>
> * Makeimg Phase
> - Creates the final NK.BIN based on stuff in the _FLATRELEASEDIR and your
> IMG flags
>
> *** Tricks to Speed things up ***
> blddemo -q
> This will skip building the Private directory. Normally, you never
> change anything here anyway so you are just wasting time calculating
> dependecies.
>
> blddemo -qbsp
> This is new in 5.0 and skips both Private and Public and only builds
> your BSP platform. This is common when you are developing device drivers
> for a BSP and didn't change the features you bring into your OS Design (no
> SYSGEN or BSP variable changes)
>
> WINCEREL=1
> When you are building something in PUBLIC and then run makeimg, you
> won't see the DLL in you Flat Release DIr (FRD) because it wasn't copied
> there. The build system only does that in the buildrel phase which you
> skipped. By setting WINCEREL=1 you get the DLL copied to the FRD as the
> last step
>
> Targeted Builds (5.0 using the IDE for your builds)
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceosdev5/h
> tml/wce50tskrunningtargetedbuild.asp
>
> Skipping makeimg by using Release Directory Modules list
> If you are debugging an image already flashed to the device, you can
> tell the CE filesystem loader to grab your DLL from your PC (in the FRD)
> rather than use the one built inside the NK.BIN. This means you can skip
> the makeimg step if your newly-built DLL is in the FRD. To do this, go to
> the Menu Target \ Release Directory Modules. This will pop-up a dialog
> that
> lets you add your DLL to the list. Now, when you reboot and debug, your
> DLL
> will come from your FRD and not the one in NK.BIN. Combined with Targeted
> Builds, this should speed you up a lot.
>
- Next message: Christopher Le [MS]: "Re: PB5.0 SDK build issue"
- Previous message: smiller: "10ms IST latency"
- In reply to: Chuck Zalinski: "RE: [Q] How to speed up build process"
- Next in thread: Dean Ramsier: "Re: [Q] How to speed up build process"
- Reply: Dean Ramsier: "Re: [Q] How to speed up build process"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
