Rebuilding in MSDEV

I am using MS Developer Studio/VC++ Version 4.2.  I have a master
project/workspace that has two sub-projects that each build an executable.
Both of these sub-projects depend on a third sub-project that builds a DLL.
 When I 'Rebuild All', Developer Studio unnecessarily rebuilds the third
sub-project twice -- once for each of the first two sub-projects that
include it.  It shoud rebuild it once for the first sub-project and
recognize that it's already been rebuilt when it goes to build the second
sub-project.  Unfortunately, the third sub-project is large, so rebuilds
are not trivial in the first place.  I have simplified the problem to only
three projects, but in reality, there is a whole tree of dependencies and
sub-projects.  This means that the project at the bottom of the tree gets
rebuilt six or eight times during a single rebuild.  Is there a patch to
Developer Studio to remedy this?  Is there a workaround to avoid this
problem?  I tried adding the third project as a sub-project for ONE of the
other sub-projects, then including the .LIB file in the linking inputs for
the other project.  This is bad, because on a normal build, the second
project won't recognize that a .cpp file in the third project has changed
and needs built.  Any suggestions?
dkgoblueAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

isakCommented:
Why are you using Rebuild, isn't it enoth to just Build?
0
dkgoblueAuthor Commented:
I am doing a 'Rebuild' because Developer Studio does not always recognize changes in ALL header dependencies (especially when there are nested includes) and, when DLLs external to the project are changed (i.e. they are built by a different project), often the only solution to get the current project and the rebuilt DLL to work together is a rebuild.  These are two examples, but I'm sure there are others my coworkers have come accross.
0
kyeckCommented:
If your project(s) link with the dll, they are dependent on the library.  VC should detect when the library has changed (when you build the dll) and force the project(s) to relink.  If this doesn't occur, I would make sure that my library path in Options/Directories is set correctly and that I've updated the dependencies for all projects.

Hope that helps,
-Ken
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.