2012/1/4 Peter Meyer <pmvs...@yahoo.de>

> Hi William,
>
> Am 03.01.2012 18:53, schrieb r...@libertysurf.fr:
> > Dear both lists,
> > I would like to understand better what is the difference between your
> two projects, in term of cross-compilation capabilities (linux ->  windows).
> > mingw-64 seems to be a much bigger project, but has not factual
> documentation on how to actually setup the cross-compiling environment.
> > I am under debian, and would like to port applications to windows.
> > Best regards,
> > William
>
> Iam not a Mingw64 Developer but a user and i do the development between
> Linux and Windows and vice versa all the time.I use MinGW64 simply as a
> 32 and 64-Bit Compiler
> on Windows only.The other Compilerproject (MinGW32), where MinGW64 cames
> from has only a Win32 Compiler.I use the MingGW64 in two diffrent
> Installations on
> Windows Vista 64-Bit as side by side Installation. A MinGW64-32-Bit and
> a MinGW64 64-Bit Installation.I target both Compiler with a 32 and
> 64-Bit Makefile and thad it is.
> MinGW64 has also a feature called Multilib thadt can handle both Targets
> 32 and 64-Bit from one Installation but i dont use it for my seld. You
> can also use MinGW64 and
> the original MinGW32 in a a mixed mode where the original Version of
> MinGW32 is used to build Win 32-Bit Builds and MinGW64 only producing
> the Win64-Builds for your
> Projects (i have tested it, and it works also very well).
>

Please remember the two projects are "MinGW.org" and "MinGW-w64". Not
MinGW32 and MinGW64, because this causes confusion and some linux packagers
project this problem onto the world.


> History:
> As far as i know. The MinGW64 Project was forked from the MinGW32
> Project because of foolery from the MinGW32 Project Staff. Some Members
> of the MinGW32
> Teams wanted to have a 64-Bit 64-Bit 86_64 Version of the MinGW Project
> but the effort was hampered by the MinGW32 Leaders.After a lot of
> discussion and flaming,
> the two teams are devided and the MinGW64 Project was created to go
> ahead with the 32 and 64-Bit Plan.
>

In a nutshell, this sounds about right (modulo MinGW32-->MinGW.org)


>
> A few notes on QT 4.7: You cannot use MinGW64 right now to compile QT
> 64-Bit on Windows, but you have to doit if you want 64-Bit Windows
> Programs (Nokia
> supports just in time only the original MinGW32 and and Visual C/C++
> Compilers not MinGW64).I tested it but there was thousands of errors at
> building QT 4.7
> with MinGW64 as Win 64-Bit Version.But If you want to use QT on Win64
> Bit with MinGW64, you have to build QT  successfully with MinGW64 first.
> After this, i switches over to GTK2 v 2.22 as Win64-Bit GUI-Toolkit wich
> works fine with MinGW64 on WinXP 32-Bit/Vista/Win7/Win8 32and 64-Bit.
> So if you want 64-Bit GUI Executables with MinGW64, i can recommend GTK2.
>

I can assure you that building Qt 4.7 and 4.8 works with MinGW-w64, both 32
and 64-bit, for every version of GCC from 4.4 to 4.7 (currently under
development). See here for old but normally still relevant instructions:
http://sourceforge.net/apps/trac/mingw-w64/wiki/BuildingQt

Ruben
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to