Run-time library to control radio transcievers and receivers

Overview Repositories Revisions Requests Users Attributes Meta

Run-time library to control radio transcievers and receivers

http://hamlib.sourceforge.net

The Ham Radio Control Libraries, Hamlib for short, is a development effort to
provide a consistent interface for programmers wanting to incorporate radio
control in their programs. Hamlib is not a complete user application, rather,
it is a software layer intended to make controlling various radios and other
shack hardware much easier. Hamlib will allow authors of such software as
logging programs, digital communications programs, or those wanting to develop
the ultimate radio control software to concentrate on the user interface and
the basic function of the program rather than radio control.

Links to hardware:sdr / hamlib
Has a link diff
Download package
Checkout Package
osc -A https://api.opensuse.org checkout home:mnhauke:sdr-devel/hamlib && cd $_
Create Badge

Build Results
RPM Lint

Refresh

Source Files

Filename	Size	Changed
_link	0000000197 197 Bytes	almost 6 years ago
hamlib-3.3.tar.gz	0002192119 2.09 MB	almost 6 years ago
project.diff	0000002225 2.17 KB	almost 6 years ago

Revision 5 (latest revision is 6)

Martin Hauke (mnhauke) committed almost 6 years ago (revision 5)

- Update to version 3.3
  * New models, R&S xk2100, TRXMAnager, Meade LX200
  * HTML manual is now generated at 'make dist' so users don't
    need GNU Info tools installed.  TNX Greg, N1DAM for the suggestion.
  * Handle longer udev generated file names up to 512 characters
  * Add debug time stamps with new '-Z' option and '--debug-time-stamps'
    options to rigctl, rotctl, rigctld, and rotctld utilities.
  * rigctld/rotctld continue working after serial or TCP device
    disappears.
  * Updates and fixes to FT-817, K3, IC-7300, AOR 3030, TM-D710,
    OMNI VII, TH-D72, Flrig, TS-590, piHPSDR, TS-2000, and netrigctl.
  * Update utility manual pages (section 1) and remove their reference
    material from the Info manual so it only needs to be update in one
    file.
  * Add new general project manual pages (section 7) and edit the Info
    manual to match.  These should not change much so keeping them in
    sync should not be too much of a burden.  The Info manual may be
    removed at some point in the future.
  * Last planned release of the present API/ABI.  Future releases will
    require recompilation and relinking by client programs using the C
    library interface (programs that only use the network daemons should
    be unaffected).

Places