64bit Qt build on WIndows

krojew

[quote author="JKSH" date="1389965053"]Hi,

I haven't encountered this message before, but...

If MSVC and/or Qt are in your system PATH, remove them. Make sure you do your compilation from the "Developer Command Prompt for VS2013"

Did you do a full clean of your build tree between compilation attempts?[/quote]

I'm using the command prompt. I've done 32 bit build earlier and did a nmake clean before 64.

krojew

After downloading git sources, the build fails on missing header files. I found that there are no headers, those without .h extension, present anywhere. I followed all git wiki instructions. Is there a way to build Qt on windows atm?

JKSH

nmake clean does not do a full clean, because there are many layers of Makefiles. You need...
@
git clean -dfx
git submodule foreach "git clean -dfx"
@

...as described in http://qt-project.org/wiki/Building_Qt_5_from_Git

I regularly build Qt on Windows and clean using the above command. No issues whatsoever. :)

krojew

I managed to find that the Perl script for generating headers did not work. For some reason, when run during full clean build, it doesn't generate any files and build just fails in the end. You have to manually execute it from qtbase first. Also there are some other errors in current git (ex. dom.cpp not seeing dom.h), but this is to be expected from a dev branch.
After some tweaking I managed to build qtbase but then failed on svg, due to syncqt.pl failing to generate anything beyond qtbase.

JKSH

The version of Perl that comes bundled with Git for Windows is old and buggy. Have you:

Installed a more recent version of Perl, and

Made sure that it is found in your PATH before the Git Perl?

Also, I recommend doing a successful compile of revision that is guaranteed to be good (e.g. the 'v5.2.0' tag in the stable branch), before trying to compile the dev branch.

krojew

I have the most recent version of Perl.

JKSH

Is it found in your PATH before the Git Perl?

krojew

Yes, it is. ActivePerl to be exact, if it makes a difference.

JKSH

ActivePerl 5.16 should work fine. This is quite odd. Could you please post the output of configure.bat, from the line that says "Running configuration tests..." onwards?

krojew

At the moment that would be quite difficult, since a clean git checkout involves me using two separate machines (don't ask...) and that takes some time. Will do that during the next few days.