Re: PBWORKSPACES and %_PROJECTROOT%
From: Gabriel Spil (gspil_at_online.microsoft.com)
Date: 10/04/04
- Next message: Dean Ramsier: "Re: Unresolved Externals creating driver"
- Previous message: Paul G. Tobey [eMVP]: "Re: Hard links/BuildRel"
- In reply to: Steve Maillet \(eMVP\): "Re: PBWORKSPACES and %_PROJECTROOT%"
- Next in thread: Steve Maillet \(eMVP\): "Re: PBWORKSPACES and %_PROJECTROOT%"
- Reply: Steve Maillet \(eMVP\): "Re: PBWORKSPACES and %_PROJECTROOT%"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 04 Oct 2004 19:27:51 GMT
In the command line build system you have two related variables, %_TGTPROJ%
and %_PROJECTROOT%. %_TGTPROJ% defines where your Project specific files
live. This includes project.* (bib, reg, etc.) files and the SYSGEN
dependency files called by %_TGTPROJ%\oak\misc\cesysgen.bat.
%_PROJECTROOT% is the location where the sysgen output files are copied and
linked to during the SYSGEN phase. By default if you have set no value for
%_PROJECTROOT% then it is set to %_TGTPROJ%. This works fine if you only
have one project. If you have multiple projects you are working on with
different sets of SYSGEN settings (ie, you have a webpad and a tinykern
project) then this is not a good solution since you have to re-SYSGEN every
time you change projects since they share the same global sysgen output
directories.
Just as %_FLATRELEASEDIR% can be set to any value so support multiple
projects, so can %_PROJECTROOT%. For example, if you use the IDE to to
manage workspaces it creates a unique %_PROJECTROOT% for each BSP_CPU and
%_FLATRELEASEDIR% for each BSP_CPU\DebugLevel mapping.
Here's an example of the values for an IDE workspace:
%_PROJECTROOT%=C:\wince500\PBWorkspaces\Tiny\wince500\Emulator_x86
%_FLATRELEASEDIR%=C:\wince500\PBWorkspaces\Tiny\RelDir\Emulator_x86_Release
If you want a unique %_PROJECTROOT% then you need to set it before calling
wince.bat.
In CE 5.0 the IDE has been unified with the command line and is just a
management layer over the command line build. You can do most tasks that
you previously did from the command line in the IDE and since the build
systems are identical anything you can't do from the IDE you can do by just
opening up a command window from the IDE. I'd recommend looking into using
the IDE since we've but a lot of features into the
Edit/Build/Download/Debug cycles to improve developer productivity.
Gabriel Spil
IDE Dev Lead
- Next message: Dean Ramsier: "Re: Unresolved Externals creating driver"
- Previous message: Paul G. Tobey [eMVP]: "Re: Hard links/BuildRel"
- In reply to: Steve Maillet \(eMVP\): "Re: PBWORKSPACES and %_PROJECTROOT%"
- Next in thread: Steve Maillet \(eMVP\): "Re: PBWORKSPACES and %_PROJECTROOT%"
- Reply: Steve Maillet \(eMVP\): "Re: PBWORKSPACES and %_PROJECTROOT%"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|