Thanks for the reply
NoQ wrote:
most of the linux users compile warzone2100 from , and it's extremely simple
That is quite an assumption to make about your users, especially for something as usually undemanding as a game; I make no apologies for the fact that I've used Debian-derivatives for nigh on 5 years, yet rely largely on the contents of software repos. In that time, I have never found a guide which makes compiling programs from source as undaunting and easy as installing from APT, or indeed even found good reason to regularly compile anything but my own work from source.
Which, IMHO, is as it should be, what with laymen's ease-of-use being APT's raison d'etre. Normal end-users should not be expected to delve into using dev packages in order to play a game with some friends. Maybe that is a sign of my ignorance (although in my defense I have coded for 2 years in Java and C; not long, but enough), but it's my opinion that there should be a divide, without overlap, between use by layperson/end-users, and use by power- or advanced users. One should be able to use a computer as one type of user, without having to become the other in normal operation.
NoQ wrote:
(in fact, the code that actually needs compiling is very small ... hardly takes 1 or 2 minutes, and since warzone is already a part of distribution, commands like apt-get build-dep warzone2100 (for debian-based distros) instantly provide you with all build-time dependencies (so you can just get the tarball and do ./configure && make and run src/warzone2100 without even installing)
Thankyou very much for the readily-given advice on compiling; that command does seemingly take the legwork out of gathering build-time dependencies, although I haven't got it to work on code which isn't in my repos; I will try again later.
Incidentally I successfully cross-compiled the 2.3.9 source tarball last night based on the cross-compile guide, so well done for providing detailed information on that. It didn't obviously mention dependencies
gettext and
libtools, possibly because they seem to be basic GNU build tools (or maybe i missed their mention in a different part of the guide), but crunchbang lacked them initially. If I had edit access to the wiki, I would be happy to help rectify any small omittals I spotted.
Like I said in my initial post, I understand that it is possible for users to manually fix this problem themselves; but, believe it or not, non-technically minded Linux users do exist, and they should not have to
compile a
source tarball (two terms i would guess they would not be familiar with) in order to effect normal usage of a piece of software.