views:

58

answers:

1

I've looked at Microsoft's MSDN and all around the web, but I still haven't been able to get a really good idea of what it is.

Does it mean the completed program loads DLLs at different times during its execution, as apposed to all at once upon launch?

Am I totally way off? :)

+1  A: 

Linking involves packaging together all of the .obj files built from your source files, as well as any .lib files you reference, into your output (eg .exe or .dll).

Without incremental linking, this has to be done from scratch each time.

Incremental linking links your exe/dll in a way which makes it easier for the linker to update the existing exe/dll when you make a small change and re-compile.

So, incremental linking just makes it faster to compile and link your project.

The only runtime effect it might have is that it may make your exe/dll slightly bigger and slower, as decribed here:

http://msdn.microsoft.com/en-us/library/4khtbfyf.aspx

Edit: As mentioned by Logan, incremental linking is also incompatible with link time code generation - therefore losing a possible performance optimization.

You may want to use incremental linking for debug builds to speed development, but disable it for release builds to improve runtime performance.

Delay loaded DLLs may be what you are thinking of:

http://msdn.microsoft.com/en-us/library/151kt790.aspx

Saxon Druce
Ah, I thought linkers always did this anyway! So, shutting off `incremental linking` will make the linker link everything from scratch each time?
Russel
"In practise the effect of this is probably not worth worrying about." it's probably worth mentioning that while the difference between "normal" linking and incremental linking may not be that great performance wise at run-time, incremental linking is incompatible with link time code generation which can make a drastic performance difference.
Logan Capaldo
@Russel: Yes it will. @Logan: Thanks, I've updated my answer.
Saxon Druce