WIndows support is likely to be extremely challenging: The erlang ABI actually has a different look to the header file. (erl_nif.h is not trivially human parsable as a result).
The correct strategy is likely to create a separate erl_nif_windows.h, and build against that.
WIndows support is likely to be extremely challenging: The erlang ABI actually has a different look to the header file. (erl_nif.h is not trivially human parsable as a result).
The correct strategy is likely to create a separate erl_nif_windows.h, and build against that.