Mon Sep 10 09:54:41 EST 2007  quozl@us.netrek.org
  * build environment setup documentation
diff -rN -u old-netrek-server/Vanilla/README.developers new-netrek-server/Vanilla/README.developers
--- old-netrek-server/Vanilla/README.developers	2007-09-10 09:55:16.000000000 +1000
+++ new-netrek-server/Vanilla/README.developers	2007-09-10 09:55:20.000000000 +1000
@@ -8,6 +8,25 @@
 with edits by James Cameron, 10th October 2002
 with edits by Zachary Uram, 25th October 2002
 
+Setting up a Build Environment
+
+    using a Debian system is easiest, since the other developers use
+    that.  It can be a virtual machine using VMware or Qemu or
+    something else.
+
+    you need certain build tools, look at Build-Depends in
+    debian/control for ideas.
+
+        apt-get install build-essential libtool autoconf automake po-debconf
+
+    you need certain software dependencies, again look at
+    Build-Depends in debian/control for ideas.
+
+        apt-get install libgdbm-dev libncurses5-dev libx11-dev \
+        libxt-dev libglib1.2-dev libgmp3-dev
+
+    test that a build completes using tests/build
+
 Source Structure
 
     ntserv/ contains the daemon process,
diff -rN -u old-netrek-server/Vanilla/autogen.sh new-netrek-server/Vanilla/autogen.sh
--- old-netrek-server/Vanilla/autogen.sh	2007-09-10 09:55:16.000000000 +1000
+++ new-netrek-server/Vanilla/autogen.sh	2007-09-10 09:55:20.000000000 +1000
@@ -1,4 +1,6 @@
 #!/bin/sh
+# autogen.sh prepares a source tree after a darcs get, see README.darcs
+# you need tools, see README.developers "Setting up a Build Environment"
 
 for file in config.guess config.sub ltmain.sh;
 do
@@ -15,3 +17,5 @@
 chmod +x debian/netrek-server-vanilla.init
 chmod +x tests/build
 echo "autogen.sh completed ok"
+
+# to test your build environment, read and run tests/build