unzig VS zig-bootstrap

I really like Zig but the unused variable error really gets in the way of how I usually do exploratory code. I've managed to produce a forked version from release 0.10.1 that adds an --allow-unused flag which disables the error. The code is hacky but it seems to work. I didn't understand a lot about Zig's caching mechanism so I might have been a little aggressive in invalidating caches when the flag is switched on and off.

I originally pulled it from here: https://github.com/markisus/unzig

It already exists. You’ll just have to compile it yourself which is relatively easy.

https://github.com/markisus/unzig

I predict / hope that in the future, the community will just host patched binaries somewhere, but for now I have gone ahead and created a patch repo whose sole purpose is to remove the unused variable error where you still have to rebuild from source. https://github.com/markisus/unzig

if you know what compiler target is used on your pi 2 you can probably get someone to cross compile it for you. https://github.com/ziglang/zig-bootstrap This should be reasonably easy to use.

Use Zig Bootstrap, it is easier. And It should work on 16gb.

you can cross compile for armv7a with zig-bootstrap

They have a project for maintaining this: https://github.com/ziglang/zig-bootstrap

I think that's the purpose of the zig-bootstrap project. By having these dependencies installed: clang, llvm, python3, cmake (notice no zig) you end up with zig compiled.

The current state is that they offer a repo with LLVM and the stage1 (C++) compiler, which should build on any system that can build LLVM (so any system with a modern C++ compiler and build tools). Or you can grab the upstream Zig code and build it against regular LLVM 12 yourself using an existing LLVM 12 clang/etc stack.