Re: [Hamlib-developer] problem adding modules (rigs)

[Stephane F. <f4...@fr...>]

Frank Singleton wrote:
> 
> David HM Spector wrote:
> > The additions/changes to testrig.c (besides setting the serial port)
> > were:
> > 
> >         retcode = rig_load_backend("r8500");
                                        ^^^^^
> >         my_rig = rig_init(RIG_MODEL_ICR8500);
> 
> For the yaesu rigs (me backend resp ), a dlopen call in  the frontend
> will
> attempt to find   the "specific" backend rig's lib.
> eg the ft747 or the ft847 lib
> 
> This should be the general case for most rigs. 
> Stephane (icom resp) may have decided to generate a general
> libhamlib-icom
> lib to handle the common icom stuff.
> 
  That's true. Almost all controlable Icom rigs support the CI-V protocol,
  including the IC-R8500 (exceptions are the PCR1000, the clonable HTs, etc.)
  Therefore, it make sense to have only one object module sharing code,
  for all these backends.

  So testrig.c should read something like this:

	retcode = rig_load_backend("icom");
	my_rig = rig_init(RIG_MODEL_ICR8500);

  Grab the latest Hamlib from the CVS rep, with a cvs checkout or from
  a snapshot at http://cvs.sourceforge.net/cvstarballs/hamlib-cvsroot.tar.gz
  and give it a shot! Let us know how it works. Also you might consider
  using rigctl for unitary tests. It has a primitive interactive interface,
  and will soon work also from command line (haha, GUIs are history :)
  As well as the icr8500 backend, this is still a WIP..

Cheers,
-- 
Stephane