StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POVS 2012 linker very slow sometimes
text
Body
copied!<p>We're using VS 2012 for a native C++ project. The project is cmake-based, and some of its dependencies (some libraries and headers) are on a network. The problem that we're facing is that with VS 2012, sometimes (1 out of 5 maybe), the linking process takes 10 minutes or more, while the same code-base links fine (in about 2 min) with VS 2010. Also, many times the code seems to be in an inconsistent state, since no break-points are hit, and some functions are not called at all (which should be). At these cases we usually restart VS or the machine if restarting VS fails which sometimes solves the problem. </p> <p>I should mention that the project is cross-platform, and compiles fine in Linux & Mac OS X, and also, with VS 2010 without any problems (during linking). The solution takes about 18 min to compile and link in windows (under normal circumstances). </p> <p>I would like to ask if there is some maintenance procedure that should be performed for VS 2012 (e.g erasing some folders) or some other action that can pinpoint or solve this problem. </p> <p><strong>Update</strong>: I would like to mention also, that the problem seems to be worse, when opening more than one VS 2012 instance, although I cannot prove it. </p> <p><strong>Update 2:</strong> The problems do not manifest, when executing the build process from the command line</p> <p><strong>Update 3:</strong> After following some advice from the MSDN forums, setting "Link Status" to YES (/LTCG:STATUS) which disables the incremental linker, seems to correct the problem with the inconsistent code state. Still, I do not know that is causing the incremental linker to fail though.</p> <p>Thanks. </p> <p>PS: VS 2012 is updated to the last available version (Update 3)</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload