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

[Frank S. <vk...@ix...>]

David HM Spector wrote:
>=20
> Hi Frank,
>=20
> The additions/changes to testrig.c (besides setting the serial port)
> were:
>=20
>         retcode =3D rig_load_backend("r8500");
>=20
>         my_rig =3D rig_init(RIG_MODEL_ICR8500);
>=20
> The file I added to the icom directrory was a modified version of the
> ic706.c file which I called "r8500.c" and there are r8500.{a|o|lo}
> files in the icom directory.
>=20
> After rebuilding everything and doing a "make install" , when I run tes=
trig I get:

>=20
> [root@wuzzle tests]# ./testrig
> testrig:hello, I am your main() !
> rig: loading backend r8500
> rig: dlopen() failed (=FF=BF =CE: cannot open shared object file: No su=
ch file or directory)
> rig_load_backend: error =3D Invalid parameter
>=20

Hmm, I just do make and skip the "make install", that way the
libs are local to my cvs directory  when I test stuff.

ie:

aclocal
autoheader
automake  --add-missing --copy --include-deps
autoconf
./configure
make

then=20

./tests/testrig=20


And things work ok.


>=20
> Am I correct in presuming that the dlopen is trying to open the
> specific rig's library module..?  Or, should it be opening "icom"
> since all of the icom-specific libraries for each individual rig
> are archived in the libhamlib-icom.a file.

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.=20
Stephane (icom resp) may have decided to generate a general
libhamlib-icom
lib to handle the common icom stuff.

I will forward this onto the hamlib devel list and see
what he says :-)

--=20
Cheers / Frank=20

73's de vk3fcs & km5ws