GNU make needed

git-svn-id: https://hamlib.svn.sourceforge.net/svnroot/hamlib/trunk@1168 7ae35d74-ebe9-4afe-98af-79ac388436b8

README.developer

@@ -89,8 +89,8 @@ General Guidelines.
 `-- yaesu
 
 
-2. Building
-2.1. Requirements
+1. Building
+1.1. Requirements
 
 Hamlib is entirely developped using GNU tools, under various Linux systems. 
 Note that it is not restricted to Linux systems. We welcome anyone who
@@ -99,13 +99,15 @@ has access to a POSIXish system to port Hamlib to. Contact us for help.
 That is, if you want to take part in the development of Hamlib, 
 you'll need at least the following tools:
 
-	* gcc
-	* autoconf > 2.50
-	* automake > 1.5
-	* libtool  > 1.4.2
+	* gcc or C99 compliant compiler
+	* GNU make  (or any modern one, BSD's isn't)
+	* autoconf >= 2.50
+	* automake >= 1.5
+	* libtool  >= 1.4.2
 	* cvs and ssh for connection to cvs.hamlib.sourceforge.net
 Optional:
 	* g++
+	* swig >= 1.3.14  for the bindings
 	* perl devel
 	* tcl devel
 	* libgd devel
@@ -146,6 +148,9 @@ This option will add new Makefile targets and dependencies.
 Tcl build, add this if needed:
 			--with-tcl=/usr/lib/tcl8.2
 
+Note: C-shell users may have to run it and make through a bourne shell instead.
+
+
 2. How to add a new backend
 	The rule is one backend per protocol family.
 	Try to share code between rigs of the same family, if applicable.
@@ -162,6 +167,7 @@ Tcl build, add this if needed:
 
 	2.5. Create mybackend/Makefile.am, mybackend.c mybackend.h
 		Use 'dummy' backend as a template.
+		Here are commands for the bourne shell.
 
 			$ automake mybackend/Makefile
 			$ CONFIG_HEADERS= CONFIG_LINKS= \