#9 Componentize .dsp files

[Nobody/Anonymous]

Logged In: YES
user_id=22738
Browser: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT; CNETHomeBuild03171999)

Problem:
How to get MidWatch to build on a small component of
a larger build.

Proposed Solution:
There should be a field in the Project List such
that each .dsp file could claim to be required for a
particular component. I.e. a .dsp file might be needed
if you your building the GUI of a product bu only when
building the GUI. Another .dsp might be required for
the GUI and the Engine of the product.
As the event is scheduled, check boxes would be
available to the user to select which components he
needed built. The build loop would skip over any .dsp
file that was not required for the selected set of
components.

What gets a little tricky is that since a .dsp file
may use an combination of configurations in the build,
a 2D matrix really whold be required to define which
configurtions are required when building a certain
component. i.e.:

.dsp Component Configurations
x.dsp GUI Win32 Release;Win32 Release Unicode
Engine Win32 Release
y.dsp GUI Win32 Release Unicode
z.dsp GUI Win32 Release;Win32 Release Unicode
Engine Win32 Release;Win32 Release Unicode
B. Logic Win32 Release;Win32 Release Unicode

Thus is only building the Engine, x & z components
would be built, but only the Win32 Release config
would be built for the x.dsp.