Provide pre-compiled static libraries.

[harry-xi]

From #1, I understand that design-wise, it should be loaded via some FFI mechanism for loading DLLs. However, considering users of native language FFIs that typically statically link other libraries, a pre-built static version would be very helpful. This is especially true given that most such FFIs usually support direct binding to C interfaces without any glue code.

[Curve]

The workflows in this repo already support building unified binaries with inlined modules, in fact, the latest actions run (https://github.com/saucer/bindings/actions/runs/21218824039) is a static build with the desktop and loop module inlined.

Static here as in, it is still one shared-library, but all modules are inlined. If this is not what you're after, I'd suggest using the upstream library directly, as using the C-Bindings as a full static library makes little sense imo.

What language are you targeting that can static link c-libraries?

[harry-xi]

The workflows in this repo already support building unified binaries with inlined modules, in fact, the latest actions run (https://github.com/saucer/bindings/actions/runs/21218824039) is a static build with the desktop and loop module inlined.

Static here as in, it is still one shared-library, but all modules are inlined. If this is not what you're after, I'd suggest using the upstream library directly, as using the C-Bindings as a full static library makes little sense imo.

What language are you targeting that can static link c-libraries?

My primary goal is Scala Native. Many programming languages that directly generate executable files, including Scala Native and OCaml, support linking directly to static libraries.

[Curve]

The workflows in this repo already support building unified binaries with inlined modules, in fact, the latest actions run (https://github.com/saucer/bindings/actions/runs/21218824039) is a static build with the desktop and loop module inlined.
Static here as in, it is still one shared-library, but all modules are inlined. If this is not what you're after, I'd suggest using the upstream library directly, as using the C-Bindings as a full static library makes little sense imo.
What language are you targeting that can static link c-libraries?

My primary goal is Scala Native. Many programming languages that directly generate executable files, including Scala Native and OCaml, support linking directly to static libraries.

Interesting. I suppose can add a configuration for static variants that have all modules inlined then :)