I've gotten Krita to build on Windows 10 64-bit - TDM-GCC 5.1.0. But just thought I mention this strange quirk, as I don't think it is suppose to happen.

I was trying to build Krita 3.0.1 (couldn't build the master branch) using MinGW via instructions in https://phabricator.kde.org/diffusion/KRITA/browse/master/3rdparty/, and it complains that it cannot find boost headers:

Code: Select all

In file included from C:/dev/krita/libs/pigment/KoColorSpaceRegistry.h:30:0,
                 from C:\dev\krita\libs\flake\KoCanvasResourceManager.cpp:30:
C:/dev/krita/libs/pigment/KoColorSpace.h:29:31: fatal error: boost/operators.hpp: No such file or directory
compilation terminated.


So it turns out the boost headers got installed into (following the folder names in the build guide):

Code: Select all

C:\dev\i\include\boost-1_61\boost

But, in KoColorSpace.h it was referencing it as follows:

Code: Select all

#include <boost/operators.hpp>

cmake was able to locate the include directory of boost under the setting "Boost_INCLUDE_DIR", but this directory was not added to the header paths in the makefile.

I can't just move the folder over since cmake is referencing that directory, so my solution (or hack) was just to copy the boost folder under the boost-1_61 folder out:

Code: Select all

C:\dev\i\include\boost

And now Krita builds and run!

So, there is probably a bug in the build process, or this info should be added to the build guide, or I'm doing something wrong. Let me hear your thoughts on this?

It's not supposed to happen...

Boost is always tiresome, I'm afraid.

I think boudewijn just pushed a commit that fixed this issue: https://phabricator.kde.org/rKRITAad5be6afefba536c3a3eb01eb9fc8fdd76a58d18

Now "Boost_INCLUDE_DIRS" cmake variable is included in header paths in Krita's build.

Yes.