Cigydd wrote: > But it keeps a standard. It was intended and designed to have exactly the same library interface. Even if it's _the same exact_ API it will definitely be different ABI. Also none of Windows synchronization objects exists on POSIX. So at the minimum you looking for a thin "shim" dll that translates calls from/to system library as a fix for different ABI. At the maximum you looking for much extensive dll that synchronizes thread states, implements wrappers around wait functions, remaps data (ex: UTF8 <-> UTF-16).
