On 19/04/2012 17:06, ext 1+1=2 wrote: >> From the homepage of project, http://mingwbuilds.sourceforge.net/ > > This is the MinGW-builds project ("mingwbuilds") > This project was registered on SourceForge.net on Mar 30, 2012, and > is described by the project team as follows: > Snapshots and releases builds of the MinGW compiler that use CRT > & WinAPI from the mingw-w64 project. Builds support the following > technologies: - OpenMP - LTO - Graphite - std Concurrency > > So, the official homepage should be: http://mingw-w64.sourceforge.net/
No, the first project is not related to the other. MinGW-builds was just recently moved from http://code.google.com/p/mingw-builds/ to http://sourceforge.net/projects/mingwbuilds, hence the new date on the Sourceforge project page. MinGW-builds only snags the *CRT* and *WinAPI* parts from the MinGW-w64 project, but is otherwise unrelated. MinGW-w64 distributes MinGW binaries which require Cygwin to run, while the MinGW-builds project distributes native Win32 versions of MinGW. Only the latter is acceptable to the Qt Project. -- .marius > Regards, > > Debao > > > On Thu, Apr 19, 2012 at 2:32 PM,<marius.storm-ol...@nokia.com> wrote: >> If you click the link in Daniels initial email, and onto the windows host >> directory, you would see that the have both the 4.7.0 release and the 4.7.1 >> prerelease as binaries already. >> >> -- >> Sent from my Nokia N9 >> >> On 4/19/12 16:14 ext Mark wrote: >> 2012/4/19<daniel.molken...@nokia.com> >> >> Hi Everyone, >> >> After several complains from the community that GCC 4.4 shipped with both >> Creator and the Qt SDK is fairly outdated (and not C++11 compliant), we are >> going to ship a mingw.org-based GCC 4.6.2 with the next Qt Creator release. >> Even though we verified that this works with the MinGW 4.4 compiled Qt >> releases from the Qt SDK, I think we should agree on a common version. Thus, >> I want to come to an agreement with all relevant stakeholders in the Qt >> Project on which MinGW to ship. >> >> From my POV, the following things are important when choosing a “proper” >> MinGW-based compiler: >> >> - Prefer existing MinGW distros* over compiling& maintaining MinGW >> ourselves (although others may disagree here) >> - Make sure they are minimal and centered around C/C++ development >> (i.e. no elaborate gjc cruft like we still have in our current MinGW 4.4 >> packages) >> - Make sure we pick a distro that provides regular updates and >> provides new GCC versions in a timely manner >> - Let’s ship both a 64 and a 32 bit version, and ideally ones that >> provide a cross-compiler respectively >> - Let’s make sure we start providing them at the same time, and we >> start building our products with them >> >> Marius found http://sourceforge.net/projects/mingwbuilds/files/, which seems >> to satisfy all of the above. Other suggestions/preferences are welcome. >> >> If deemed necessary, we can also build our own MinGW distro via Qt Project’s >> public build infrastructure (http://builds.qt-project.org). We need good >> build recipes for that, though, and someone who is willing to maintain them. >> >> Cheers, >> Daniel >> >> *) by “Distro” I mean different entities compiling& providing MinGW >> releases such as MinGW.org, TDM, etc >> >> >> >> >> Why not wait till there is a MingW with GCC 4.7.0 release? I'm asking that >> since GCC 4.7 adds support for AVX and AMD bulldozer (bdver1) specific >> compiler optimization which seem to be greatly beneficial for AMD cpu's. So >> it might be worth the consideration to postpone the next Qt Creator release >> till there is a MingW with GCC 4.7.0. >> >> >> Just my opinion. >> >> >> Cheers, >> Mark >> _______________________________________________ >> Development mailing list >> Development@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
