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

Re: The mingw* mess in Debian

On Fri, 25 Nov 2011 14:03:32 +0100, Fabian Greffrath <fabian@greffrath.com>
> > probably generate more confusion with the similarity to mingw32. I'd vote
> > for mingw-w64-i686 and mingw-w64-x86_64 in the end, based on the
> > following:
> Me too!

I'll go for that then, taking into account Simon's remark (so -x86-64).

> > How about the following base description:
> >
> >   MinGW-w64 provides a development and runtime environment for 32- and
> > 64-bit (x86 and x64) Windows applications using the Windows API and the
> > GNU Compiler Collection (gcc).
> Sounds very good!


> > As far as the packages are concerned, the mingw-w64 source package would
> > produce mingw-w64, mingw-w64-i686, mingw-w64-x86_64, the corresponding
> > three -dev variants and a single -tools package (since that varies only
> > by host
> With "the corresponding three -dev variants" you mean a meta-package 
> mingw-w64-dev, which depends on both mingw-w64-i686-dev and 
> mingw-w64-x86_64-dev?

That's exactly what I had in mind.

> > architecture); gcc-mingw-w64 would produce all the gcc-based packages
> > (gcc-mingw-w64, gcc-mingw-w64-i686, gcc-mingw-w64-x86_64; I'm also
> > splitting
> Will gcc-mingw-w64 also be a meta-package which depends on both 
> gcc-mingw-w64-i686 and gcc-mingw-w64-x86_64?


> > the package up into gcc, g++, gnat, gfortran etc.) including the
> > transitional gcc-mingw32 package; likewise binutils-mingw-w64 and
> > gdb-mingw-w64.
> On which package will the transitional gcc-mingw32 package depend? On 
> gcc-mingw-w64-i686 with compatibility symlinks to the binaries to take 
> account of the changed GNU tupel?

To provide all the binaries in gcc-mingw32 it will have to depend on
{gcc,g++,gfortran}-mingw-w64-i686; its only contents will be the
compatibility symlinks you mention (and the usual /usr/share/doc contents).
It will pull in mingw-w64-i686-dev indirectly, and binutils-mingw-w64-i686

As I understand it having the mingw-w64 package produce a gcc-mingw32 package
will make the gcc-mingw32 source package disappear eventually...



Attachment: signature.asc
Description: PGP signature

Reply to: