1moon-buggy - drive some car across the moon 2 3 4INTRODUCTION: 5 6 Moon-buggy is a simple character graphics game, where you drive some 7kind of car across the moon's surface. Unfortunately there are 8dangerous craters there. Fortunately your car can jump over them! 9 10 Moon-Buggy comes with NO WARRANTY, to the extent permitted by law. 11You may redistribute copies of Moon-Buggy under the terms of the GNU 12General Public License. For more information about these matters, read 13the file COPYING of the source code distribution or press 'c' at 14moon-buggy's title screen. 15 16 Please mail any suggestions and bug reports to <voss@seehuhn.de>. 17Your message should include the moon-buggy version number, as obtained 18by the command 'moon-buggy -V'. 19 20 21INSTALLATION: 22 23 Moon-buggy requires the curses library as a prerequisite. If 24curses is not installed on your system, you may use the free ncurses 25package. The game does not work with BSD curses, thus on BSD systems 26you will need the ncurses package. 27 28 Generic installation instructions are in the file INSTALL. There 29are some points of interest: 30 31 * By default, the program will be installed as 32 '/usr/local/bin/moon-buggy'. You can specify an installation 33 prefix other than '/usr/local' by giving 'configure' the 34 '--prefix=PATH' option. 35 36 * You can choose the score file's location via 'configure''s 37 '--sharedstatedir' option. On Linux you should use 38 39 --sharedstatedir=/var/games 40 41 to comply with the Filesystem Hierarchy Standard. 42 43 * Moon-buggy supports shared score files. As explained in 44 moon-buggy's manual, you may want to make moon-buggy a setgid 45 program. This can be done with the '--with-setgid' option. If 46 you use 47 48 --with-setgid=games 49 50 then the installation process arranges everything for setgid usage. 51 52 CAUTION: this introduces potential security risks. I tried to 53 minimise these, but nevertheless be careful with this. And 54 remember: moon-buggy comes with no warranty. 55 56 * If your version of the curses library is not autodetected, you 57 have to use some of the '--with-curses-includedir', 58 '--with-curses-header', and '--with-curses-libs' options. For 59 example you should use 60 61 --with-curses-includedir=/usr/pkg/include 62 63 if your curses header files are in "/usr/pkg/include/". You may 64 use 65 66 --with-curses-header="<mycurses.h>" 67 68 if your curses header is called "mycurses.h". And you may use 69 70 --with-curses-libs="-L/usr/pkg/lib -lncurses" 71 72 if your curses library is called "ncurses.a" and is located in 73 "/usr/pkg/lib/". 74 75 76 Example: On GNU/Linux systems you probably can use the following 77commands. For the last one you need root user permissions. 78 79 ./configure --sharedstatedir=/var/games --mandir=/usr/share/man \ 80 --with-setgid=games 81 make 82 make install 83