<ohsix>
google has one or three things to build chrome/their tools that are interesting but i'm unfamiliar with them, as long as you don't have to write 'tests' for features with cmake it's alright
<whitequark>
ohsix: oh well that answers it
<whitequark>
in-tree builds are not supported by solvespace buildsystem (but are supported by cmake, in principle)
<ohsix>
as soon as you need to write tests -> autotools, ti comes with a ton of standard feature tests but it's also easy to write more
<ohsix>
hm k
<whitequark>
cmake has tons of tests and makes it extremely easy to write those
<whitequark>
see solvespace/cairo
<whitequark>
and solvespace/angle
<whitequark>
thats way easier to read than autotools stuff
<whitequark>
I literally prefer handwritten makefiles to autotools
<whitequark>
not to mention the incredible pain in the ass that is upgrading autotools
<ohsix>
yea you can't read it
<ohsix>
also when you don't know autotools already, and you try and look at peoples build files it's really hard to figure out what is right, which is unusual
<ohsix>
api as macros is weird too
<ohsix>
cmake has support for different configurations which can be important to windows
<ohsix>
like a debug target
<whitequark>
yeah, autotools are not an option for solvespace
<whitequark>
because I need to build using MSVC
<ohsix>
but back to solvespace, even if it's unsupported, isn't it fixable?
<ohsix>
you can get autotools to generate a config.h or even build files, but yea; if you're not using mingw to cross build it's all bad
<whitequark>
not cross
<whitequark>
solvespace is built with msvc on windows
<ohsix>
yea, not cross would be msvc, hehe
<ohsix>
even if you have a config.h for windows you don't have build files that say what component is part of which bit
<whitequark>
yup
<ohsix>
my consideration for autotools includes basically having a linux package manager around, heh; getting even part of that up on windows sucks
<ohsix>
hm, it can't be a subdir either? make[2]: *** No rule to make target '../res/freedesktop/solvespace-48x48.png', needed by 'res/freedesktop/solvespace-48x48.png'. Stop.
<whitequark>
hm? of course it can be a subdir...
<whitequark>
did you bork your source tree perhaps?
<ohsix>
that's a few clean, cmake .., make -jx builds
<ohsix>
i realize that it shouldn't be in the same order every time :p
<ohsix>
it hasn't happened again in like 20 retries, i think it is just a small race window and probably ignorable unless you're building on a machine that is swapping ;]
<ohsix>
i restarted chrome earlier, last night it was doing it every time
<travis-ci>
solvespace/solvespace#166 (master - d151eb5 : whitequark): The build passed.