From: Berndt Josef Wulf <wulf@ping.net.au>
To: Stephane Fillod <f8cfe@free.fr>,
Hamlib developers <hamlib-developer@lists.sourceforge.net>,
Linux HAMs <Linux-hams@vger.kernel.org>
Subject: Re: [ANN] Hamlib 1.2.3 released
Date: Sat, 20 Nov 2004 17:50:18 +1030 [thread overview]
Message-ID: <200411201750.27373.wulf@ping.net.au> (raw)
In-Reply-To: <20041119221617.GE3052@charybde.local>
[-- Attachment #1: Type: text/plain, Size: 2630 bytes --]
G'day,
is there a particular reason why hamlib has bindings such as tcl and perl
enabled by default? I believe that it makes hamlib more complex and difficult
to maintain as a package due to the increase of inter-library dependencies
and bloads a standard installation unnecessarily.
It doesn't seem to make sense that "./configure --help" reports options
--with-perl-binding, --with-tcl-binding etc. when it really isn't as they are
enabled by default. I had to explicitly add configure arguments
--without-<name>-binding in order to stop building these.
Bindings didn't get build by default in previous version.. Am I missing
something here?
73, Berndt
VK5ABN
On Saturday 20 November 2004 08:46, Stephane Fillod wrote:
> Good news everyone!
>
> Hamlib-1.2.3 has been released.
>
> Hamlib provides a unified environment for the development of radio and
> rotator control applications. Release 1.2.3 includes many fixes since
> last official version. A strong emphasis has been put on backend
> addition and fixes.
>
>
> Check it out at http://hamlib.org !
>
> New in 1.2.3:
> * frontend API: LEVEL_SQLSTAT marked as deprecated
> * new backends: Racal, V4L radio cards, Watkins-Johnson 8888
> * new models: IC-78, IC-7800, IC-R20, IC-756PROIII
> * fixes: AOR 5k&8k: added S-Meter, 7030: fixed freq,
> IC-R8500: calibrated S-Meter, legacy Jupiter and many others..
> * port: mingw32 dist with gcc 3.4 version, and stdcall interface
> to prepare for VisualBasic support.
>
> Download pages are accessible at http://sourceforge.net/projects/hamlib
> i386 rpms and .deb coming soon. Win32 DLL's are already available.
>
>
> Please, test it out and report to hamlib-developer@lists.sourceforge.net
> Developers are also invited to join the Hamlib team by subscribing to
> this mailing list. If your favorite rig is not in the supported list,
> feel free to ask.
>
>
> Many thanks to all the developers and testers who participated
> in this release.
>
> Have fun and let us know!
>
> 73's de Stephane - F8CFE / the Hamlib team
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Hamlib-developer mailing list
> Hamlib-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
prev parent reply other threads:[~2004-11-20 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 22:16 [ANN] Hamlib 1.2.3 released Stephane Fillod
2004-11-20 7:20 ` Berndt Josef Wulf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411201750.27373.wulf@ping.net.au \
--to=wulf@ping.net.au \
--cc=Linux-hams@vger.kernel.org \
--cc=f8cfe@free.fr \
--cc=hamlib-developer@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox