hamradio/Hamlib
1
0
Fork 0
mirror of https://github.com/Hamlib/Hamlib.git synced 2024-09-21 10:27:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

GNU make needed

Browse Source 
git-svn-id: https://hamlib.svn.sourceforge.net/svnroot/hamlib/trunk@1168 7ae35d74-ebe9-4afe-98af-79ac388436b8
This commit is contained in:
Stéphane Fillod, F8CFE 2002-09-10 06:43:05 +00:00
parent 9b82982c18
commit b31a6ddaea
1 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.developer
View File

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