Am 01.03.2017 um 21:19 schrieb alvinpenner:
on Windows 10, current trunk, I normally execute the following two Cmake commands: mingw32-make -j 2 mingw32-make install
The time required for this is 300 seconds, 150 seconds for each step. This time is the same no matter how small the change, even if I just insert one single blank character somewhere. Previously, using btool, the total time required for this would be about 10 seconds or so, for a complete rebuild of Inkscape. So CMake is about 30 times slower than btool, which makes it almost impossible to do diagnostic work with Inkscape, any way of speeding it up?
Alvin
Hi Alvin,
I can confirm this behavior. What takes that long is scanning dependencies (i.e. CMake checks which dependencies every file has and if one of those changed and a rebuild of that file is required). This step seems to be especially slow on Windows, probably due to slower file IO compared to *nix.Therefore every build will take some minimum time, even if no files changed. On my machine it was considerably faster though (~45 s if I remember correctly), but still annoying when working on something.
To solve this issue I'd recommend you to use ninja to build instead of ming32-make. I have that successfully running on Windows 10 now and incremental rebuilds only take ~10s. I documented the necessary steps in our Wiki not long ago: http://wiki.inkscape.org/wiki/index.php/CMake#Using_CMake_with_Ninja_to_buil...
Regards, Eduard