Tracking issue for Zig #113
Labels
area: infrastructure
Issues related to infrastructure (GitHub, CI, etc).
state: blocked
Issues that are blocked on some other issue/work.
type: housekeeping
Issues that are classified as cleanup or refactoring work.
This is a tracking issue for this Zig wiki page.
For context, the Zig SDK is an MSBuild SDK that vastly simplifies the process of building and integrating native components written in Zig or C-family languages into .NET solutions and NuGet packages. Ordinarily, this is a very annoying process as users have to rely on separately-installed native compilers and figure out cross-compilation themselves. Zig's unmatched cross-compilation story and support for C-family languages are the killer features that enable this whole project; the SDK itself is mostly a whole bunch of glue logic that bridges the .NET build ecosystem with the
zig
command line interface.These are the issues that either currently affect us or will do so in the future:
__DllMainCRTStartup@12
when building a DLL targetingi386-windows-msvc
ziglang/zig#11926 - This prevents us from building C-family DLLs for 32-bit x86 Windows. I would much rather that this platform was allowed to die, but unfortunately, that doesn't seem to be happening anytime soon, so we do need this.zig cc -MJ
(forcompile_commands.json
) does not work well with multiple files ziglang/zig#9323 - We currently have to do some really unfortunate hacks due to-MJ
support being broken.Overall, we're very happy with Zig. It is bringing real value to the .NET ecosystem, not just through this project, but also this one!
The text was updated successfully, but these errors were encountered: