rules_mojo 🔥
Hey, I just published
rules_mojo, an hermetic, reproducible way to build Mojo with Bazel and Nix, supporting all x86_64-linux distros ❤️
https://github.com/TraceMachina/rules_mojoGitHub
GitHub - TraceMachina/rules_mojo: A bleeding edge build system for ...
A bleeding edge build system for Mojo 🔥. Contribute to TraceMachina/rules_mojo development by creating an account on GitHub.
4 Replies
nice!
I've just pushed an update that adds the following:
- A bundled C++ toolchain so that it's no longer necessary to have a host C++ toolchain preinstalled. This toolchain uses the
mold linker which makes efficient use of multi-core machines for link time speedups of up to 95%.
- The mojo command now works and starts the REPL. mojo build and mojo package also work and use the bundled C++ toolchain.
- Improved the hermeticity of system libraries. Previously the Remote exec toolchains were a bit brittle when invoked from hosts that had an older glibc than what nixpkgs uses. Now all rpaths are pinned to the hermetic nix variants.That’s really really impressive, deep respect
We switched over to a new cluster setup. This improves cluster startup time from ~20min to 8 min on a GH runner and to ~2 min on a "regular" local machine.
Still figuring out some issues with the latest nightly. I'm super happy to see that
tinfo is no longer linked by default though. I removed the tinfo dependency from LLVM and it looks like that trickled down to the mojo cli 😆