Dmitrijs Ledkovs wrote:

> There are currently two free implementations of msvcrt: mingw.org and 
> mingw-w64.
> Programs built with mingw32 *unable* to safely use DLLs built with
> mingw64 there are subtle differences in implementations.

That answers my main question.  Then I suppose:

> We have one ABI (windows-like) and then for OS parts it could be
> "native" - msvcrt or "unix-like" - cygwin. For free kernel options we
> have ReactOS and linux+wine. For msvcrt we have options of using mingw
> and w64. So maybe something like this:
>
> Debian name:
> ms-msvcrt
> ms-cygwin

mingw32-winnt
mingw64-winnt
mingw32-msys
mingw64-msys
mingw32-cygwin
mingw64-cygwin

(Obviously I am not attached to the names, just trying to figure
out which targets need distinct Debian names for compatibility.)

Presumably at the moment you're be working on mingw64-winnt?

> And then it's up to Debian maintainers which msvcrt implementation
> (analogy with libc) to use - mingw.org or w64 (this one). We can
> package both to test and compare and find bugs, etc.

Ah, interesting.

Thanks again.  Others wiser than I am can presumably take it from
here.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to