On 7 May 2013 05:38, Stephen Kitt <sk...@debian.org> wrote: > Hi Wookey, > > On Tue, 7 May 2013 03:04:50 +0100, Wookey <woo...@wookware.org> wrote: >> (just a decision to leave arch-independent headers in /usr/include and >> move arch-dependent headers to /usr/include/triplet). > > Doesn't this limit us to cross-compiling only across Debian architectures? If > we go for a full /usr/include/triplet split (in the same way as for > libraries) we could support cross-compiling to anything with the same > structure - I'm thinking MinGW-w64 here of course, but I imagine it would > apply to other targets too, some of which are supported in Debian already > using the /usr/triplet/include directories. >
I for one believe that MinGW-w64 should become partial architectures on debian (both 32 and 64bit variants... and arm?! =) ). Partial as it would use linux kernel + wine for runtime. Having mingw as an arch will greatly make it easier to provide an up-to-date archive of deb package that one would reasonably would want to cross-compile against. And with some luck and NSIS magic create .exe installers to redistributed compiled packages to Windows. I am patiently waiting for bug #606825 dpkg: Please add mingw to ostable and triplettable. To be fixed. As well there is interest in developing i686/x86_64-w64-mingw32 [1] port. And doko has also informally voiced support for such a triplet name at last debconf. [1] Yes, exactly these i686/x86_64-w64-mingw32 and not other proposed combinations. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
