By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,365 Members | 3,095 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,365 IT Pros & Developers. It's quick & easy.

Incremental linking doesn't work - SOLVED

P: n/a
I've been having trouble getting incremental linking to work under Visual
C++ .net 2003 7.1 for my multi-project workspace. Ronald Laeremans and Carl
Daniel (and a few others) helped me figure it out.

Short answer: I should never have expected incremental linking to work.

Short answer addendum: Linking is slower in 7.1/.net/2003 than VC++6.

===

My multi-project workspace consisted of one ".exe" project and about 40
".lib" projects. Making a change in one cpp/obj of a .lib would cause my
exe to be re-linked. This took a few seconds in VC++6. In
VC++7.1/.net/2003 this takes two minutes.

This huge increase in time led me to believe VC++7.1/.net/2003 was not
incrementally linking, while VC++6 was. However, I now believe that neither
version was incrementally linking. The new linker is just much slower than
the old. (You can't incrementally link static libararies).

Fast Solution Build
(http://www.workspacewhiz.com/FastSol...ildReadme.html
) modifies the build process to pass all the objs to the linker (and not
send the .lib) which enables "incremental linking" for people who have many
..lib projects in their workspace.

Until I can find a way to bring VC++71/2003/.net link times down to VC++6
levels (is there anything I can do?), I'll just use "Fast Solution Build".

Thanks for your help everyone,

Rudy

PS: Pass "/test" to link.exe to find the reason a link is not incremental.
Nov 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.