Zig is a programming language with strong C interoperability, making it particularly easy to include C dependencies in Zig projects (and vice versa) -- in fact, Zig can compile C code (using either a native bootstrap or LLVM), and the build.zig scripts can serve as a (frankly saner) alternative to CMake even for pure C projects. Zig also comes with built-in cross-compilation support, including to WASM.
All this being said, would you consider distributing Zig build scripts (two files only: script and manifest) for utf8proc? If so, I can make a PR upstreaming the ones used by Neovim. I understand that taking on maintenance for additional tooling -- that you don't use yourself -- is not very appealing, especially since Zig is still heavily in development. At least I can promise that these files won't bitrot easily since they'd be exercised by Neovim (and covered by CI). But if you deem this out of scope, feel free to close this issue and no hard feelings!
Zig is a programming language with strong C interoperability, making it particularly easy to include C dependencies in Zig projects (and vice versa) -- in fact, Zig can compile C code (using either a native bootstrap or LLVM), and the
build.zigscripts can serve as a (frankly saner) alternative to CMake even for pure C projects. Zig also comes with built-in cross-compilation support, including to WASM.All this being said, would you consider distributing Zig build scripts (two files only: script and manifest) for
utf8proc? If so, I can make a PR upstreaming the ones used by Neovim. I understand that taking on maintenance for additional tooling -- that you don't use yourself -- is not very appealing, especially since Zig is still heavily in development. At least I can promise that these files won't bitrot easily since they'd be exercised by Neovim (and covered by CI). But if you deem this out of scope, feel free to close this issue and no hard feelings!