I'm following the instructions as given here: https://phabricator.kde.org/diffusion/K ... /3rdparty/

My OS is Windows 10 64bit.

Now stuck when building Qt 5.6.1 (cmake on ext_qt). Here is the build error message:

Code: Select all

In file included from qoffscreenintegration.cpp:46:0:
..\..\..\..\include\QtPlatformSupport\5.6.1/QtPlatformSupport/private/qbasicfont
database_p.h:1:89: fatal error: ../../../../../src/platformsupport/fontdatabases/basic/qbasicfontdatabase_p.h: No such file or directory compilation terminated.
Makefile.Release:971: recipe for target '.obj/release/qoffscreenintegration.o' failed
mingw32-make[10]: *** [.obj/release/qoffscreenintegration.o] Error 1
Makefile:34: recipe for target 'release' failed
mingw32-make[9]: *** [release] Error 2
Makefile:65: recipe for target 'sub-offscreen-make_first' failed
mingw32-make[8]: *** [sub-offscreen-make_first] Error 2
Makefile:96: recipe for target 'sub-platforms-make_first' failed
mingw32-make[7]: *** [sub-platforms-make_first] Error 2
Makefile:660: recipe for target 'sub-plugins-make_first' failed
mingw32-make[6]: *** [sub-plugins-make_first] Error 2
Makefile:41: recipe for target 'sub-src-make_first' failed
mingw32-make[5]: *** [sub-src-make_first] Error 2
Makefile:50: recipe for target 'module-qtbase-make_first' failed
mingw32-make[4]: *** [module-qtbase-make_first] Error 2
ext_qt\CMakeFiles\ext_qt.dir\build.make:117: recipe for target 'ext_qt/ext_qt-prefix/src/ext_qt-stamp/ext_qt-build' failed
mingw32-make.exe[3]: *** [ext_qt/ext_qt-prefix/src/ext_qt-stamp/ext_qt-build] Error 2
CMakeFiles\Makefile2:1358: recipe for target 'ext_qt/CMakeFiles/ext_qt.dir/all' failed
mingw32-make.exe[2]: *** [ext_qt/CMakeFiles/ext_qt.dir/all] Error 2
CMakeFiles\Makefile2:1370: recipe for target 'ext_qt/CMakeFiles/ext_qt.dir/rule' failed
mingw32-make.exe[1]: *** [ext_qt/CMakeFiles/ext_qt.dir/rule] Error 2
Makefile:416: recipe for target 'ext_qt' failed
mingw32-make.exe: *** [ext_qt] Error 2


The error doesn't make a lot of sense, since the file it is looking for is actually present.

Huh... No, that definitely doesn't make sense at all! Building Qt always fails a couple of times for various reasons, but this is the first time I've seen this failure.

Did you follow the instructions as closely as possible? Or did you make slight modifications like using different source and build paths? Were you building in a Windows Command Prompt (i.e. cmd.exe) or some kind of MSYS or Cygwin shells? Were you doing a clean build?

When you say the file is present, did you actually followed the relative path to ensure that the directory depth is correct?

Perhaps if you can somehow manage to find what the actual command CMake used to build Qt is, it might give a better clue. It might be somewhere among the generated Makefile.

Also, try cleaning and rebuilding if you haven't.

Or did you make slight modifications like using different source and build paths?

Nope. Followed as close as I can.

Were you building in a Windows Command Prompt (i.e. cmd.exe) or some kind of MSYS or Cygwin shells?

I'm using command prompt.

Were you doing a clean build?

Yep, it's a clean build. I wiped out the "ext_qt" folder once and tried again for good measure.

When you say the file is present, did you actually followed the relative path to ensure that the directory depth is correct?

yep.

@alvinwong is ur build on windows also? And you succeeded following all the instructions in the README?

Ok. This is very interesting. All I did was moved the dev folder to C drive from D drive.

Just like that, Qt 5.6.1 builds, and the mysterious file missing errors disappears.

I'm not sure if when the guide says,

Make a toplevel build directory, say $HOME/dev or c:\dev.

It meant you must use "C:\dev". But that doesn't make sense either.

Maybe it's because my compiler (TDM-GCC 5.1.0, as specified) is installed there. Maybe it's because my OS (windows 10 64-bit) is installed there. Maybe it only works when in the root directory in a drive. Maybe it had something to do with includes using <> or "" in the source code (which wouldn't make sense, since only very specific files under the "platformsupport" folder are affected). At any case, the build times are waaaay to long for me to explore these. I rather focus on other things.

I also had build errors when I used the python that ships inside Anaconda 4.1(https://www.continuum.io/downloads), cause I had Anaconda in my PATH and it has its own versions of the libraries Krita uses, but that's a minor issue compared to this.

The $HOME/dev is for Linux or OSX developers. I always use c:\dev myself, but I know that windragon has built on f:\dev...

boudewijn wrote:The $HOME/dev is for Linux or OSX developers. I always use c:\dev myself, but I know that windragon has built on f:\dev...

More precisely it's F:\dev\krita


... actually it's F:\dev\krita\krita for source, F:\dev\krita\build_3rdparty and F:\dev\krita\build_krita for building... not to mention that I built Qt separately...

But yeah, they are all under the same drive letter.