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

[John R. <js...@ho...>]

Stephane,

Thanks! That worked.

I did a configure with --prefix as you suggested, then a make install.

I shouldn't have been trying to avoid doing that.

John

rm -f testrig testrig.o

export HAMLIB=/usr/local/hamlib/
export LD_LIBRARY_PATH=${HAMLIB}/lib:.

gcc -DHAVE_CONFIG_H -I${HAMLIB}/include -D_GNU_SOURCE -g -O2 -Wall -c 
testrig.c
gcc -g -O2 -Wall -o testrig testrig.o -L${HAMLIB}/lib -lhamlib

./testrig


>From: Stephane Fillod <f4...@fr...>
>To: Ham...@li...
>Subject: Re: [Hamlib-developer] How to link in binary
>Date: Tue, 27 Nov 2001 19:12:27 +0100 (MET)
>
>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
>
>_______________________________________________
>Hamlib-developer mailing list
>Ham...@li...
>https://lists.sourceforge.net/lists/listinfo/hamlib-developer


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp