One of our VS2010 solutions contains two static libraries that are built with /Qipo in release configuations. These are then linked into a console application project and a DLL project, also with /Qipo set. The link phase for the console application and the DLL takes well over 10 minutes each; I would like to improve this. Disabling IPO in the console application and DLL projects significantly reduces link times, but also significantly impairs the performance of the application, so while useful for experimenting, this is not desirable for production use.
The documentation suggests that the /Qipo[n] and /Qipo-jobs options (amongst others) may help with build performance, but they do not have IDE equivalents and specifying them as additional options in the Command Line property page for the static library or console application projects seems to have no effect.
Any suggestions for improving our link times would be welcome.
We are using Intel Fortran Composer XE 2013 Update 1 for Windows.