From: Nate B. <n0...@n0...> - 2013-04-18 02:57:06
|
* On 2013 17 Apr 17:05 -0500, Stephane Fillod wrote: > I would strongly advise NOT to use hamlib3 for stable end-user programs. > The ABI and API of Hamlib3 is supposed to change even more, so no > official release any time soon. I'd recommand instead to use hamlib 1.2.x > for programs and MXE. Should Makefile patchs be backported (cherrypicked) > from Hamlib3 area, so be it. Except for RPC daemon support, Readline, and Texinfo support I've yet to push, I am going to guess that the configure.ac from Hamlib 3.0 would work in the 1.2 series with a bit of work. The reason I didn't get too aggressive porting the Autotools changes over to 1.2.15.x is stability and predictability. Once serendipity stepped in and removing some obsolete tests caused the rig/rot daemons to start working on MS Windows, I was happy enough to stop! That said, I am not opposed to porting many of the changes in the build system to 1.2.15.4 and beyond espcially if it keeps that branch viable for MXE or other environments. > fldigi is in desperate need of a build with an updated hamlib (latest 1.2.x). > Couple of minutes glory for the one bringing Hamlib1.2 to the MXE build > environement, so fldigi Windows users (among others) benefit from it. What Fldigi is in desperate need of is being dynamically linked to Hamlib so that testers on platforms other than Linux/BSD can also drop in a newer version of Hamlib without having to rebuild Fldigi. Modularity is a Good Thing (TM). </RANT> > Thanks Remi for working on making Hamlib available for MXE, Agreed! Many thanks, Remi. I appluad your efforts with MXE. 73, de Nate >> -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us |