---- Jasper van de Gronde <th.v.d.gronde@...528...> wrote:
On 08-03-12 21:52, Johan Engelen wrote:
Hi all, I would like to have an IRC meeting about the build system on Windows.
Although I like buildtool, it cannot do parallel builds, so I am happy to change (back) to something else. And unify it with Linux if possible... I am trying cmake now, but it does not link without errors yet. It is not very encouraging to see the cmake build process get stuck on some intermediate step for a long while, seemingly checking something to find out it does not need to rebuild it. "btool" does this much much quicker...
In any case, I'd like to discuss the options. Who's in?
Depends on when the meeting is, but I wouldn't mind participating.
And here's an alternative option: use buildtool on Linux as well. Seriously. Yes, buildtool has its deficiencies, and it is much less flexible than *make, but it is /so/ much easier to use and maintain (the build file itself I mean, not buildtool). I'm completely unaware of the issues involved in getting it to work on Linux, so perhaps it's just not very feasible. Or perhaps I'm unaware of some of the issues buildtool has on Windows. But I would hate to see buildtool go and be replaced by some other monster of a build system just because it couldn't do parallel builds (which should in principle be fixable).
(Obviously non-monster build systems are welcome to apply, but I haven't seen many of those.)
One idea I had is that, whichever buildsystem we use, we could just hardcode the library stuff for windows, and force people to use the devlibs ;-) I think what makes it hard to maintain is trying to make it find libs automatically, set the correct link flags, etc. But perhaps I am wrong :) If someone wants to spend time and make buildtool do parallel builds, I am happy too.
-Johan