Create Targeted Builds (Compact 7)
3/12/2014
A targeted build builds only what has changed, and therefore gets code changes to the OS run-time image as fast as possible. Targeted builds are especially useful when you are repeatedly changing the same code modules.
The main challenge in creating a targeted build is tracing the downstream dependencies of what you are building. The following diagram shows the algorithm for tracing them.
.png "Improve Build Process Targeted Build Preparation A")
Finding the path of the sources file for a .lib, .dll, or .exe file can be performed from the command line using findstr /sip library_name sources, or by using a full text search in Windows Explorer.
You may find that, with practice, performing targeted builds becomes second nature and that you significantly reduce the time you spend on builds.
If your dependency tree becomes complex (10 or more nodes), a targeted build may actually be slower than running the appropriate blddemo command.
In This Section
- Targeted Build Example: Public Tree
Provides an example of building from the public tree.
- Targeted Build Example: Common or Platform Tree
Provides an example of building from the common or platform tree.