Important: Please read the Qt Code of Conduct -

Using configure on Windows VS2005 x64

  • I'm trying to understand what is going on when I run configure. The first time I can configure I ran it with something along the lines of:

    .\configure -debug-and-release -opensource -plugin-sql-mysql -plugin-sql-sqlite -plugin-sql-psql -platform win32-msvc2005 -system-zlib -qt-libpng -qt-libmng -qt-libtiff -qt-libjpeg -no-freetype

    This proceeded to compile for a considerable time before halting because it was looking for a psql include file. I didn't really need this anyway and I didn't want to go tracking that down so I ran configure again omitting the -plugin-sql-psql.

    My question is why did nmake then start recompiling everything? I was thinking it would just pick up at the sql plugins and continue. Does the build system have no dependency checking at this level? It wasn't obvious to me where I would have disabled psql without running configure and perhaps its best not to know ;-)

    This isn't a huge deal since I'll end up with a build eventually but it since its taking 4ish hours to do a build I'd like to know what I can and can't change without incurring a full rebuild.


    • James

  • If you reconfigure then a generated header file, qconfig.h, will be regenerated, containing some info about what parts of Qt are enabled. That means everything which includes that header will be recompiled, which is most of Qt.

    You might be able to speed up your build by using vcbuild or jom, either of which should be able to parallelize to some degree (unlike nmake).

Log in to reply