Re: [Hamlib-developer] How to link in binary

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

John Roberts wrote:
>
> Here is the script I'm using to compile:
> 
> rm -f testrig testrig.o
> 
> export HAMLIB=../hamlib-1.1.2/
> export LD_LIBRARY_PATH=${HAMLIB}/.libs/:${HAMLIB}/icom/.libs:.
> 
> gcc -DHAVE_CONFIG_H -I${HAMLIB}/tests -I${HAMLIB}/include -I${HAMLIB}/src  
> -D_GNU_SOURCE  -g -O2 -Wall -c testrig.c
> gcc -g -O2 -Wall -o testrig testrig.o -L${HAMLIB}/src -lhamlib
                                        ^^^^^^^^^^^^^^^^
If you're not using hamlib-devel RPM, then use "-L${HAMLIB}/.libs"
instead of -L${HAMLIB}/src. This is what libtool would do for rigctl.

Anyway, I strongly recommends using the hamlib-devel RPM in your case,
unless you want to help in bleeding edge Hamlib development. Nevertheless,
with the cvs version, it's still better to configure hamlib with 
--prefix=/usr/local or whatever (and set -L/usr/local/lib accordingly) 
and then "make install".

Let me know how it goes. If bands are still open, we can have a sked.

73, Stephane