Support zig cc, have instructions for building outside of devcontainer

[remexre]

It sounds like we could just have zig cc build the right cross-compilation toolchain. The pain of getting the right dependencies then goes way down. We should support this in ./configure and write docs for how to configure it, plus a note that like, you can just use an appropriate host toolchain.

This probably depends on #79, since AFAIU zig cc is always backed by Clang.

For the ./configure interface, maybe we should add a --zig-cc flag that's mutually exclusive with --clang, and makes $CC be ignored in favor of $ZIG, then sets up the appropriate toolchain for the target.

[arbormoss]

Is it possible there would be one solution for doing both something like this and #30 ? Like a docker-compose that uses the devcontainer image?

It could have services that can be run with docker compose run <service>, and each service runs the required commands. This is mostly how I'm thinking of doing #30 anyways. It seems like there might be some way to make the interface also work as a way to build without a state-sponsored IDE. /sar

Ofc it would still be using the docker image and not actually building without a container.

[remexre]

uh, not sure about the services angle; what daemons are you expecting to need?

i'd imagine that if you wanted to use a devcontainer with e.g. vim, you'd just do docker run -it whatever, and install+run vim inside that container

by "outside of the devcontainer," i really mean "on alpine/debian/whatever, with instructions other than 'install (vscode|nix|podman), then [...]'." i think "a suitable toolchain for cross-compiling" is our only weird dependency; zig replaces that.