[Hamlib-developer] Builds of shared and static libraries

[Nate B. <n0...@n0...>]

Going through the issue list I found issue #1500:

https://github.com/Hamlib/Hamlib/issues/1500

Wherein Mike notes that it should be possible to build both shared and
static libraries.  I thought that odd as I seemed to recall that in the
past both were built as SOP.  I spent some time with configure and its
options and not working out why it was either/or.

Not thinking (we could probably stop right there) that it was anything
to do with Hamlib I posted to the libtool mailing list seeking some
help:

https://mail.gnu.org/archive/html/libtool/2025-04/msg00005.html

A kind soul by the name of Simon helped out and pointed out a section in
our configure.ac file that sets the variables that control shared and
static libraries in an exclusive OR fashion.  The use of 'git blame'
showed this section was added in the following commit:

https://github.com/Hamlib/Hamlib/commit/43159e55a1c4351199fada21eb6be4632001d930

My testing shows that commenting that section enables the default
libtool behavior of building both shared and static libraries and
dynamically linking the executables (rigctl, etc.) to the shared
library.  I've also tested the Windows 32 and 64 bit binaries and I
don't see any build issues (I've not tested run time).

I've looked through the closed issues, the discussion and mailing list
archives, and even my private mail and don't see anything that prompted
that commit.  Even more puzzling is the opening of the issue two and a
half months later.

Regardless, it is my intent to temporarily revert that commit by
commenting the relevant lines and seeing who yells.  🤔

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819