[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#648306: The mingw* mess in Debian

On Tue, 29 Nov 2011 12:17:54 +0000, Wookey <wookey@wookware.org> wrote:
> I know almost nothing about mingw* use and variants, but it does strike
> me that it just another cross-compiler, and choices about package
> names and triplets should be at least influenced by what we do for all
> the other cross-toolchains, multiarch considerations and
> dpkg-architecture support.
> This was discussed a long time ago on the debian-embedded list and
> this page covers using dpkg-architecture and dpkg-cross to help with
> cross-building debian-style for mingw32:
> http://wiki.njh.eu/Cross_Compiling_for_Win32 (It predates multiarch
> but the fundamentals are there).
> Would it be useful for dpkg to know about w32-i386 and thus to be able
> to use all the dpkg-cross and/or multi-arch machinery to help when
> crossbuilding for win32? If so then is there anything in what you are
> doing that gets in the way of this?

The specifics regarding mingw-w64 have been discussed in the past; there's
an open bug against dpkg at http://bugs.debian.org/606825 which includes part
of the discussion. The result there was that we'd use mingw64...

I haven't taken care of all that yet; I'm waiting for the dust to settle
around multiarch before integrating cross-compiler stuff following the same
ideas (Steve Langasek mentioned a while back that the first priority was to
get multiarch working, without considering cross-compiler issues
particularly, even though there are similarities).

In any case what we've discussed so far in this thread is compatible with the
discussion in the above-mentioned bug.



Attachment: signature.asc
Description: PGP signature

Reply to: