[Releasing] Compiling Qt 5 alpha 20120314: msvc2010 release build

[Rohan McGovern]

Thiago Macieira said:
> On segunda-feira, 19 de março de 2012 09.49.34, Rohan McGovern wrote:
> > One problem with having any part of Qt disabled by default is
> > that there is not actually a way to _enable_ such parts again via
> > configure arguments.
> > 
> > Well, Unix configure has -nomake and -make (e.g. -nomake tests disables
> > tests, -make tests would enable tests if they were disabled by default).
> >
> > Windows configure.exe however has -nomake to disable parts, and no way
> > to _enable_ parts.  (There is a -make option but it has entirely
> > different meaning than on Unix).
> 
> We have an option to enable the tests. Throughout Qt3 and Qt4, the tests were 
> enabled by -developer-build

The tests should be possible to enable for non-developer-build
configurations, since that is the configuration which the majority of Qt
users are supposed to use, and we ought to be able to test it.

> or by the LICENSE.TROLL file's presence. Why don't we do the same?

It's needlessly obfuscated for one thing.  How many people do you think
actually knew this? :)

I'm simply suggesting that the tests are treated like other parts of the
build (e.g. like examples): they're a subtree which can be entirely
enabled/disabled at configure time.  But that enabling/disabling
mechanism is not very good at the moment.