Closed YOU54F closed 5 months ago
Just a note on:
dll.lib
is a static lib that contains the glue code to load the DLL on Windows. It will be used with C/C++ projects using MS Visual C++ (if that still exists). Ie. you link the dll.lib
to your project, and that exports the functions from the DLL that auto-load the DLL when invoked.Also, on the .so
for musl, there is an issue with that as that .so
shared lib will contain the musl libc linked into it. It may only work on Alpine versions that use the same version of musl. If it is used with other versions, it can lead to stack corruption and segmentation violations. In essence, a different .so
lib needs to be built for every version of Alpine.
dll.lib
for windows, everything I've seen usesdll
only.a
, used for musl builds? not sure how, would love to hear from Alpine users, I had to generate an.so
file and use it that way.so
file for alpinepact_ffi
/pact_verifier_cli
/pact_mock_server_cli
release workflow would be made redundant by this workflow as it is also catered for.
Warrants a conversation about nomenclature with regards to platform / architecture. I've got a few thoughts.
Pact-Reference Supported Platforms / Architectures
Legend
Pact-Reference Target Matrix
Unofficial Pact-Reference Target Matrix
target lists taken from