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

[kj4tmp]

ok it looks like I have been down this path before and I have just forgotten lmao:

Windows GNU/MingW and MSVC binary C ABI compatibility guarantees

This question is a bit of a follow-up to the recent Cross-compiling for Windows: What is the difference between `-gnu` and `-msvc`? How binary compatible are the -windows-gnu and -windows-msvc C ABIs, in theory and in practice? Imagine I want to compile an executable for x86_64-windows-gnu. I have a library compiled for x86_64-windows-msvc (either by Zig or MSVC or some other compiler). Will I be able to link my executable with the library when the library is static (.lib or .a) the library …

Cross-compiling for Windows: What is the difference between `-gnu` and `-msvc`?

When cross-compiling for windows from linux, what is the difference between using targets: zig build -Dtarget=native-windows-gnu zig build -Dtarget=native-windows-msvc ? It appears that -msvc is impossible to do from linux if I need to link libc, because I would need to install the windows sdk on linux which is impossible?

Compiling windows project: error: 'ip2string.h' file not found #include <ip2string.h>

I am cross compiling from linux to windows -msvc. If you can accept microsoft visual studio license, you can use xwin to download the windows sdk and the microsoft c runtime. The command line, include paths, and library paths: zig translate-c windows.h · GitHub