On 26/03/2014 15:09, Bill Somerville wrote:
Hi All,
A somewhat belated correction here, sorry I thought I had replied to the list to someone about this.

my recent changes really need to be built against a version of Hamlib with many changes over the current release version. For now (until they are all accepted into Hamlib) you can get the soure by:

git clone https://[email protected]/u/bsomervi/hamlib <your-source-path>/hamlib-latest

Should read:

git clone git://git.code.sf.net/u/bsomervi/hamlib <your-source-path>/hamlib-latest


The master branch has all of the accepted changes but for the latest and greatest you need to switch to the 'integration' branch:

cd <your-source-path>/hamlib-latest
git checkout integration

I build this using a MinGW environment from an msys console with commands like:

./autogen.sh --enable-shared --disable-static --prefix /c/test-install/hamlib
make && make install

it requires MinGW C & C++, autoconf and libtool

On Linux I use:

./autogen.sh --enable-shared --disable-static --prefix $HOME/test-install/hamlib
make && make install

On Mac:

You need to install autoconf and libtool. I recommend MacPorts.org for a way to install these tools in a pain free manor. Because there is a libtool on Mac that does a different job you need to have libool built with a 'g' program prefix. Using MacPorts does this for you out of the box.

To build do something like:

LIBTOOLIZE=glibtoolize M4=gm4 ./autogen.sh --enable-shared \
   --disable-static --prefix=$HOME/test-install/hamlib --disable-winradio
make && make install


Another new prerequisite on Windows is OmniRig. OmniRig is a MS COM server so to build against it you need to have OmniRig installed, this is quite painless and it is a small footprint. You can get it from Alex's website:

http://www.dxatlas.com/omnirig/

Just do a default install and then forget about it (unless you actually want to use it to interface to a rig).

More to come...

73
Bill
G4WJS.
73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

Reply via email to