Jonathan Liu:
Also, GCC 4.7.x has problem where it runs out of
memory in some cases (https://bugs.archlinux.org/task/28329).
I just checked for the i686 and x86_64 - all ok.
--
Regards,
niXman
___
Dual-target(32 64 bit) MinGW compilers for 32
On 31/08/2012 2:16 AM, Thiago Macieira wrote:
On quinta-feira, 30 de agosto de 2012 17.25.24, Pau Garcia i Quiles wrote:
There are more differences than that. There are differences in
features, such as threading support, large-file support, etc.
Mingw-w64 is usually ahead of any other in terms
On Sat, Sep 1, 2012 at 1:58 PM, Peter Kümmel syntheti...@gmx.net wrote:
What is the problem with the current thread support in mingw?
When you compile the gcc, you can choose which thread model do you
want to use: win32 or pthread.
In case of pthread the gcc will use the winpthreads package for
[mailto:development-bounces+kai.koehne=nokia@qt-project.org] On
Behalf Of ext Thiago Macieira
Sent: Thursday, August 30, 2012 6:17 PM
To: development@qt-project.org
Subject: Re: [Development] Choosing a new MinGW for Qt 5
On quinta-feira, 30 de agosto de 2012 17.25.24, Pau Garcia i Quiles wrote
On 03.09.2012 16:10, kai.koe...@nokia.com wrote:
My suggestion on how to proceed is to choose one that offers the following or
most of the following:
- most recent GCC (4.7 preferably, 4.6 if not)
Latest mingw-builds and latest rubenv packages both provide 4.7.1
- *working* GDB and
On 30.08.2012 18:16, Thiago Macieira wrote:
On quinta-feira, 30 de agosto de 2012 17.25.24, Pau Garcia i Quiles wrote:
There are more differences than that. There are differences in
features, such as threading support, large-file support, etc.
Mingw-w64 is usually ahead of any other in terms
SEH32 : patented by MSFT
It's actually Borland's patent and Borland said they only patented
that to defend themselves from third-party attacks, they have no
interest in attacking gcc:
http://web.archive.org/web/20070818053531/blogs.codegear.com/dcc/archive/2005/05/12/4294.aspx
I wonder if
On sábado, 1 de setembro de 2012 12.23.31, Peter Kümmel wrote:
As a general rule, you should choose the default SJLJ packages,
unless you know you need faster exception handling and can guarantee
you'll never need to unwind through non-DW2-compiled stack frames
(such as
On 01.09.2012 12:39, Thiago Macieira wrote:
On sábado, 1 de setembro de 2012 12.23.31, Peter Kümmel wrote:
As a general rule, you should choose the default SJLJ packages,
unless you know you need faster exception handling and can guarantee
you'll never need to unwind
On 01.09.2012 12:47, Peter Kümmel wrote:
On 01.09.2012 12:39, Thiago Macieira wrote:
On sábado, 1 de setembro de 2012 12.23.31, Peter Kümmel wrote:
As a general rule, you should choose the default SJLJ packages,
unless you know you need faster exception handling and can
On 01.09.2012 12:52, Thiago Macieira wrote:
On sábado, 1 de setembro de 2012 12.47.15, Peter Kümmel wrote:
So you think it is possible to use DW2 for 32 bit binaries?
Yes.
What happens if a binary compiled with GCC/DW2 calls a
C++ function in a Dll compiled with MSVC and this function
On 31.08.2012 09:02, Pau Garcia i Quiles wrote:
All those MinGW and forks contain mingw32-make.exe util which does have -j
option, but in fact this option doesn't make the real parallel build. Maybe
sh.exe is needed, but this shell util will pass the incompatible path string
so that the build
On 30.08.2012 18:16, Thiago Macieira wrote:
On quinta-feira, 30 de agosto de 2012 17.25.24, Pau Garcia i Quiles wrote:
There are more differences than that. There are differences in
features, such as threading support, large-file support, etc.
Mingw-w64 is usually ahead of any other in terms
Hi,
On Fri, Aug 31, 2012 at 3:34 AM, Yang Fan missd...@gmail.com wrote:
Currently, official MinGW project provides GCC 4.7, but it uses SJLJ
exception mode when TDM/MinGW-w64/MinGW-build projects use Dwarf2 exception
mode which is known as zero-overhead exception.
I forgot to say we now have
Yes, I was trying make -j option under the msys environment one or two
weeks ago, and it gave incompatible path string and broke my building
process. My msys was installed through official MinGW installer or from the
Git for Windows project, both have the same problem.
On Fri, Aug 31, 2012 at
] Choosing a new MinGW for Qt 5
On quinta-feira, 30 de agosto de 2012 17.25.24, Pau Garcia i Quiles wrote:
There are more differences than that. There are differences in
features, such as threading support, large-file support, etc.
Mingw-w64 is usually ahead of any other in terms of features.
My
On 30.08.2012 18:16, Thiago Macieira wrote:
My suggestion on how to proceed is to choose one that offers the following or
most of the following:
- most recent GCC (4.7 preferably, 4.6 if not)
- *working* GDB and tested with Creator, with Python support
- large file support, threading
On Fri, Aug 31, 2012 at 3:00 PM, kai.koe...@nokia.com wrote:
Alright, since there are people both in favor of mingw-builds and mingw-64 I
guess we have to do a proper comparison :)
Question to the mingw-64 supporters: Which exact package should we evaluate?
On sexta-feira, 31 de agosto de 2012 16.05.14, Peter Kümmel wrote:
On 30.08.2012 18:16, Thiago Macieira wrote:
My suggestion on how to proceed is to choose one that offers the following
or
most of the following:
- most recent GCC (4.7 preferably, 4.6 if not)
- *working* GDB and
Hi,
I'd like to get this on the table again: What is the MinGW package that we want
to support officially? The matrix for Qt 5.0 right now says MinGW gcc 4.5 32
bit [1]. Note that when you're installing latest mingw from mingw.org it's
already installing gcc 4.7, and I guess you'd need to dig
, August 30, 2012 4:57 PM
To: Storm-Olsen Marius (Nokia-MP/Austin); pgqui...@elpauer.org
Cc: development@qt-project.org
Subject: [Development] Choosing a new MinGW for Qt 5
Hi,
I'd like to get this on the table again: What is the MinGW package that we
want
to support officially? The matrix
Hi,
On Thu, Aug 30, 2012 at 4:56 PM, kai.koe...@nokia.com wrote:
Hi,
I'd like to get this on the table again: What is the MinGW package that we
want to support officially? The matrix for Qt 5.0 right now says MinGW gcc
4.5 32 bit [1]. Note that when you're installing latest mingw from
Rubens release is currently broken, and there shouldn't be a need for a
separate package for 32bit vs 64bit really.
--
.marius
On 30/08/2012 10:05, ext Loaden wrote:
I want to say, mingw-w64 is the best choice.
I am using ruben's personally build to compilation Qt5/QtCreator on both
Windows
It's can be fixed just replace the mingw32-make.exe.
And it's the best choice to separate package for 32bit vs 64bit really.
-m32 and -m64 will possible can't works well on Windows.
2012/8/30 marius.storm-ol...@nokia.com
Rubens release is currently broken, and there shouldn't be a need for a
On 8/30/12 6:16 PM, ext Thiago Macieira thiago.macie...@intel.com
wrote:
On quinta-feira, 30 de agosto de 2012 17.25.24, Pau Garcia i Quiles wrote:
There are more differences than that. There are differences in
features, such as threading support, large-file support, etc.
Mingw-w64 is usually
Currently, official MinGW project provides GCC 4.7, but it uses SJLJ
exception mode when TDM/MinGW-w64/MinGW-build projects use Dwarf2 exception
mode which is known as zero-overhead exception.
All those MinGW and forks contain mingw32-make.exe util which does have -j
option, but in fact this
26 matches
Mail list logo
