Open CrazyboyQCD opened 3 days ago
Is it worth considering whether we should just defer to the Zig build system? Then, the build script could just clone the source repo and invoke zig build. Lots of libraries do this with C dependencies and CMake, so it might be the path of least resistance.
Alternately, we could move away from Zig entirely and just make our own custom CC or CMake script. This might not be that difficult - all of the source files required are identified in the build.zig I think. Then we could leverage the existing Rust CC or CMake crates.
It's worth noting that this would primarily be beneficial for projects like Firefox where there is a requirement to vendor all dependencies. For my own project, I don't need this and so I don't plan to work on this personally :)
Is it worth considering whether we should just defer to the Zig build system? Then, the build script could just clone the source repo and invoke zig build. Lots of libraries do this with C dependencies and CMake, so it might be the path of least resistance.
That's why I think this may be unnecessary.
Alternately, we could move away from Zig entirely and just make our own custom CC or CMake script. This might not be that difficult - all of the source files required are identified in the build.zig I think. Then we could leverage the existing Rust CC or CMake crates.
I don't know which is easier to maintain, this needs to investigate.
It's worth noting that this would primarily be beneficial for projects like Firefox where there is a requirement to vendor all dependencies. For my own project, I don't need this and so I don't plan to work on this personally :)
Since mach's source code haven't been updated for nearly a year, I will invetigate if I could apply https://crates.io/crates/mach-siegbert-vogt-dxcsa to the latest one.
Target
Build from source code with rust.
Steps
DrawBack
This requires amounts of time and work and may be unnecessary.