Removed README_VB as its info is now embedded in the build-VB.NET.sh
script and is output into a custom README file upon creation of the ZIP
archive.
Added README.scripts to document reason for the directory and included
scripts.
The scripts/ directory will contain helper scripts for building Hamlib
binary releases for Win32 and possibly other target platforms. EAch
script should be accompanied by a companion README file with information
on the script and build requirements.
Initial release of build-win32.sh for building Win32 DLLs and EXEs for
use with MS VC++.
README - Add info on availability, compiling, and version.
README.betatester - Remove info relevant to developers, include 'make'
targets, add info on rigctl verbosity.
README.developer - Add note on developer Git acces via SSH,
Clean up leftover file from bundled libtool. The autoconf script will
provide a symlink to the system installed install-sh for the version of
automake installed.
Create new confparams token of 'ritclr' for clearing RIT/XIT offset
without turning off RIT/XIT function. Thanks to Tor, N4OGW, for the
request. May be replaced in the future by a dedicated RIT/XIT clear
function in the Hamlib API.
As the K3 does not return a response to the AN? set command, direct the
backend to use kenwood_set_ant_no_ack() instead. Thanks to Alexander
Sack, KC2ZSX for catching this.
Wayne Burdick, N6KR, advises that the forthcoming KX3 (prototype
shown at Dayton Hamvention 2011) will have an identical command
set to the K3.
Fix K2 and K3 backend versions.
The call to usb_set_configuration() looks troublesome for the setup
for the FUNcube dongle on Win32 target. In fact it appears not to be
necessary (TBC). Make that call optional per backend choice.
Updated README.release procedure and configure.ac for Windows DLL (mingw32)
build. Now that hamlib no longer bundles libltdl (libtool), libltdl must
be imported, configured with --host-i586-mingw32msvc, and built (before
configuring hamlib with --host-i586-mingw32msvc).
Sockets under Windows require specific startup and cleanup calls.
Besides, the standard fdopen() does no work on socket descriptors,
and has to be worked around thanks to _open_osfhandle().
Master branch, a.k.a. "trunk" branch for main development, will now have
its numeric version string appended by '~git'. Per Kamal Mostafa,
KA6MAL, the use of the '~' character causes packaging systems to treat
the version string as an ealier release. e.g. The Debian packaging
system treats 1.2.14~git as earlier than 1.2.14 which is useful to
avoid confusion after release.
Bill reports his TS-440 returns 38 chars instead of the default 29.
This patch defines iflen of 38 for the ts440 backend and implements
necssary support in the ic10 backend.
git-svn-id: https://hamlib.svn.sourceforge.net/svnroot/hamlib/trunk@3067 7ae35d74-ebe9-4afe-98af-79ac388436b8
Nate Bargmann