4 ms·
Right. But switching build systems is a big ask for a lot of situations. The build workflow is part of the API for a lot users of that project.
by humanrebar 4y ago
Right. But switching build systems is a big ask for a lot of situations. The build workflow is part of the API for a lot users of that project.
- messe 4y agoJust because it’s the default doesn’t mean it’s the only option. Another approach would be to integrate your zig code as a static library, and have your existing build system call out to zig’s build system just for that part of the build. Linking it to the rest of your code could then be performed by your existing build system, just as it would link any other library. In practice, Zig is quite flexible.
- humanrebar 4y agoI'd like that plan a lot more if there were any normal way for build systems to communicate about build requirements and outcomes and the zig toolchain implemented it.
- messe 4y agoThat’s as much make’s fault as Zig. You can go further and eschew the zig build system, using `zig build-lib`, I’d that helps.