Building self-hosted from the original C++ implementation

Help
13

I needed another silly fix for zig3 in callsites

Hm, that shouldn’t be necessary with the right order of operations. Let me be a little more specific:

  • Have zig3 from some commit <= 7b2a936173165002105ba5e76bed69654e132fea
  • With that commit checked out, apply my patch
  • Update zig1.wasm
  • Before building another zig3, check out, at a minimum, 08b2d491bcd8c79c68495267cc71967661caea1e to update the usages

Because just updating zig1.wasm won’t use the C backend, your patch shouldn’t be necessary; you can just let the next commit update all the usages before you try to make any updated zig3.

Sure! It’s all here:

Amazing, thanks for the link!

2 Likes