[Development] Building Qt5.2 under Visual Studio 2013

Mojmír Svoboda Mojmir.Svoboda at warhorsestudios.cz
Mon Oct 7 14:05:15 CEST 2013

* Nagy-Egri M?t? Ferenc <nagymatef at freemail.hu> [2013-10-07 11:23:26 +0000]:

> Should the error be addressed on the project side or be reported to MS
> and hope a fix comes before final version?

ICE are almost always on MS side. Often you can find some workaround
until they fix it. For example sometimes only rearranging includes works
(i.e. change the compilation conditions a bit). Sometimes you'd have to
use different code.. it really depends on the nature of ICE.

Step 1: Google. You may find already some similar bug report that may
have some workarounds mentioned in it.

Step 2: Isolate the ICE and report it
MS is not willing to do anything unless they *really* have to, so what
you have to do is isolate the ICE in some few line example so that they
fetch it to the programmers and shout "bad programmer, bad!".

Otherwise you'll end up in some never ending indian customer care loop,
which is very very annoying.

Step 3: (maybe) Use another (older) compiler

Also may be worth noting that msvc 2010 to 2012 tends to generate
occasional ICE (few times a day), but luckily these are benign: when you
run the compilation again, it does not show up.

Have a nice day,

More information about the Development mailing list