Both shared and static libraries?

[jas4711]

Thanks for 3.0.0, I've finalized Debian packaging of it, and it sits in the NEW queue due to the ABI bump.

One change I noticed since 2.x is that static libraries were dropped. I see there is a STATIC_ON flag but that disables shared libraries. Is it possible to build both a shared and static library, like before?

I don't think this is important, I doubt many people care about having a static library shipped via Debian, but it was one thing I noticed as a difference so wanted to bring it up. Maybe the cmake magic is simple, I'm sure there are many other libraries built via cmake that supports building both shared and static version at the same time.

/Simon

[kaoh]

I have implemented the proposed dual shared/static library build on the issue-129-dual-library-builds branch.

On Unix-like systems, the default CMake configuration now builds and installs both libglobalplatform.so and libglobalplatform.a (and the PC/SC plugin equivalents). -DSTATIC=ON remains a static-only compatibility mode. The CMake exports and pkg-config metadata were updated for static consumers.

The complete packaging matrix passed in CI, including Linux DEB/RPM packages, macOS packages, Windows packages, and x86/x64 Windows SDK archives: https://github.com/kaoh/globalplatform/actions/runs/32854972736

Could you please test this branch with the Debian packaging workflow and confirm that the usual single build now provides the static archive for libglobalplatform-dev alongside the shared runtime library? Feedback on the package split and any downstream compatibility issues would be useful.