Checking interest for cargo-cross replacement with cargo-zigbuild

[mislavn]

Before making a PR I wanted to check if there's a need for it.

At work I started with cargo-cross but later moved to cargo-zigbuild because I could avoid using docker/podman locally and in the CI.

I know you also add clang/openssl/sqlite3 in the docker images so I don't know how useful it is. I could add a nix flake to make a reproducible build environment but that requires Nix and I think that's a bigger overhead than cargo-cross for most users.

[banditopazzo]

the cross base images are very old having openssl 1 and that's an issue for dynamically linked binaries, basically right now you are forced to link openssl statically or use rustls because current distros dont ship openssl 1, or maybe some of them ship it as a compat lib.

because of that issue I was exploring the idea of using a custom base image, maybe a very recent so we can have latest versions of build tools and dev libs and using zig as a linker to lower just the libc dependency.

but I had to pause this task because I have no time right now