Build process is a big entry barrier
Posted: Fri Mar 03, 2006 10:27 pm
Hi all,
I've been interested in the project (MOO was probably the game I've wasted most of my time until now...). My PC runs Linux (Ubuntu, Debian-based). I've found the build process to be incredibly hard to setup. Following the Debian instructions from "Harm" didn't help much. I've skimmed through the forum, and found phrases like "the developers don't have the time to keep the libraries up to date". If that's the case, shouldn't a binary version of the libraries be shipped with the code so the bugs are reproducible for all developers???
I understand one of the libraries is not open-source and couldn't be shipped in this form. Why was it selected? Seems like an obtuse solution, it must be a lot better than anything else available... I hope.
In the same rant, I'd like to say I could only unzip the data.zip file on windows - Linux complained about not having a central directory or something alike (sorry, I'm not on Linux at this time).
Thanks!
[]s Gus
I've been interested in the project (MOO was probably the game I've wasted most of my time until now...). My PC runs Linux (Ubuntu, Debian-based). I've found the build process to be incredibly hard to setup. Following the Debian instructions from "Harm" didn't help much. I've skimmed through the forum, and found phrases like "the developers don't have the time to keep the libraries up to date". If that's the case, shouldn't a binary version of the libraries be shipped with the code so the bugs are reproducible for all developers???
I understand one of the libraries is not open-source and couldn't be shipped in this form. Why was it selected? Seems like an obtuse solution, it must be a lot better than anything else available... I hope.
In the same rant, I'd like to say I could only unzip the data.zip file on windows - Linux complained about not having a central directory or something alike (sorry, I'm not on Linux at this time).
Thanks!
[]s Gus