Re: Long period to check for dependencies for the initial build
From: ssggys (anonymous_at_discussions.microsoft.com)
Date: 04/19/04
- Next message: Michel Verhagen [eMVP]: "Re: Taskbar Auto Hide"
- Previous message: K. S. Huang: "Re: Defining serial port IRQ"
- In reply to: Steve Maillet \(eMVP\): "Re: Long period to check for dependencies for the initial build"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Apr 2004 15:39:45 +0800
Thanks for reply. How about in Embedded Visual C IDE ? I need to wait
for long period on the 1st time I open up EVC and compile my code, any
advise ?
ssggys
Steve Maillet (eMVP) wrote:
> It's not checking dependencies per se. It's doing the sysgen phase of the
> build. Lot's of things happen at this point. All of the header files are
> filtered according to the various OS feature sets selected so that your
> platform has header files that match exactly the APIS you have included. The
> sysgen phase also builds the component libraries into EXEs and DLLs. This
> keeps only the functionality you requested in each EXE or DLL and insures
> that the importlib for the DLL only has the APIS actually included. All of
> this filtering and processing takes time. You can shorten it somewhat by
> manually setting the _DEPTREES environment var for your project to list ONLY
> the OS project folders (under %_WINCEROOT%\public) that your platforms
> depends on.
>
> The good news is that this phase only needs to run when you make OS feature
> selection changes. If you change your own code it's not needed.
>
- Next message: Michel Verhagen [eMVP]: "Re: Taskbar Auto Hide"
- Previous message: K. S. Huang: "Re: Defining serial port IRQ"
- In reply to: Steve Maillet \(eMVP\): "Re: Long period to check for dependencies for the initial build"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
