开云体育

Hi again.

Looking into this now.? But...

These steps mentioned by Dave 'HKJ...

How to add a new transceiver to flrig

(A)
? Two new files will need to be added:
??? . src/include/RIGFAMILY/NEWRIG.h
??? . src/rigs/RIGFAMILY/NEWRIG.cxx
Done OK.? (Blank for now...)


(B)
? Three files will need to be modified:
??? . Makefile.am
?????? add the references to the two new files
Unable to even find references to any existing rig files, so at a loss what to add here.


(C)
??? . src/include/rigs.h
??? . src/rigs/rigs.cxx
?????? add the references to the new rig
Done, referencing the new rig's files created as the first step(A)


? RIGFAMILY might be icom, yaesu, elad, etc.
? NEWRIG might be IC-9999, FT-9999, etc.
Understood, but see above.

Suggest using an existing rig (.cxx, .h) files as a template for
the new rig.? Choose a file that will use similar CAT commands.

After the new files have been added and the three files updated
you will need to recreate the build scripts.? From the top level
flrig directory:

? $ autoreconf
? $ ./configure
? $ make

David


What exactly do I add to makefile.am?? As above, there is nothing there I can see, that references other rig files in an obvious way.

All that is in there at present, is :-

ACLOCAL_AMFLAGS = -I m4
SUBDIRS = src

if DARWIN
appbundle:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif

if HAVE_NSIS
nsisinst:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif

#EXTRA_DIST = build-aux/config.rpath


That to me, looks more like what platform to build for, not what sources to build from..

Or (again) have I missed something?


73.

Dave G0WBX.

-- 
Created on and sent from a Unix like PC running and using open source software: