Writing runtime-extensible code in Zig is massively inconvenient

[kj4tmp]

@cancername

Can you elaborate? In general, C code without bit-fields is easy to make ABI-safe. Or do you mean different libcs being incompatible?

My previous struggles linking MinGW to MSVC libs:

Can I link binaries produced using MSVC to zig executable targeting GNU?

I am building an executable that depends on npcap. My strategy for depending on it is to link against the npcap-sdk (downloaded using the zig build system as a dependency in build.zig.zon), which is provided as pre-compiled static libraries and headers. As far as I can tell, these binaries are produced using Visual Studio, which I am guessing means they are MSVC ABI? Can I cross-compile my executable from x86_64-linux to x86_64-windows-gnu and expect it to work? Why or why not? As of now, I …

(it hasn’t crashed yet but i’m still a bit scared )