Build shared and static libs on the same run?

--2f4uf5gtv32tqk2f
Content-Type: text/plain; protected-headers=v1; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Subject: Build shared and static libs on the same run?
MIME-Version: 1.0

Hi All.

I've been involved with the Hamlib project for many years.  I seem to
recall that at one time both .so and .a libraries were built by libtool.
The project uses Autoconf, Automake, and Libtool, so I think this list
is the obvious choice to ask my question.

I recent years I have observed that only .so binaries are built unless
--enable-static is passed to the 'configure' script.  The result is that
=2Ea libraries are built but no .so libraries and all of the user
executable programs are static linked to the new libraries.

In 'configure.ac' the following macros are used:

LT_PREREQ([2.2.6b])
LT_INIT([win32-dll])
LT_LANG([Windows Resource])

As a test I tried with just a bare LT_INIT request and saw no change
with only .so libraries being built by default.

I am working through a list of issues of the project and one is a
request to build both .so and .a libraries by default.  Hence the
motivation for this email.

I am building Hamlib on Debian GNU/Linux 12 with libtool 2.4.7.  I also
do separate builds for MS Windows, but I don't that is a part of this
discussion.  I can provide links to files for examination if requested.

- Nate

--=20
"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
NIT([win32-dll])

--2f4uf5gtv32tqk2f
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCZ/RlTQAKCRD7LFEw1VqI
GfQ1AKCD5EJLgvoJFqD9inhdfZutJlaQ4QCff/gMQBelJhDpfqjuVD+kiwzRT3A=
=TLqE
-----END PGP SIGNATURE-----

--2f4uf5gtv32tqk2f--