From: Ruben V. B. <van...@gm...> - 2013-01-19 20:26:57
|
Hi, I have updated the Qt wiki on MinGW-w64: http://qt-project.org/wiki/MinGW-64-bit It has a nice explanation (which was *wrong* on many accounts until now) of various "stuff". I'm attempting to build the prereqs now, I might upload them when I succeed. Also: it seems the Qt Project chose for "posix" threading for all the wrong reasons in their own release to public installers, and has no idea of the possible performance impact. It will be positive to get winpthreads and posix threading out in the wild though :-) Cheers, Ruben |
From: Алексей П. <al...@gm...> - 2013-01-19 20:32:29
|
Hi, Ruben! I also has this work done in my Qt-builds on https://github.com/Alexpux/Qt-builds. With my scripts no possible do full build of Qt-4.8.4(not tested yet), Qt-5.0.0, Qt-5.0.1 with all Qt prerequisites and dependencies except Microsoft DirectX SDK. Binary builds now hosted on https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds . 2013/1/20 Ruben Van Boxem <van...@gm...> > Hi, > > I have updated the Qt wiki on MinGW-w64: > http://qt-project.org/wiki/MinGW-64-bit > > It has a nice explanation (which was *wrong* on many accounts until now) > of various "stuff". > > I'm attempting to build the prereqs now, I might upload them when I > succeed. > > Also: it seems the Qt Project chose for "posix" threading for all the > wrong reasons in their own release to public installers, and has no idea of > the possible performance impact. It will be positive to get winpthreads and > posix threading out in the wild though :-) > > Cheers, > > Ruben > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > > |
From: niXman <i.n...@gm...> - 2013-01-20 18:22:32
|
2013/1/20 Алексей Павлов: > Hi, Ruben! > I also has this work done in my Qt-builds on > https://github.com/Alexpux/Qt-builds. With my scripts no possible do full > build of Qt-4.8.4(not tested yet), Qt-5.0.0, Qt-5.0.1 with all Qt > prerequisites and dependencies except Microsoft DirectX SDK. Binary builds > now hosted on > https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds. Alexey once again surprised everyone by writing a script to build Qt from the box =) Thanks for a great job, Alexey! -- Regards, niXman ___________________________________________________ Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingwbuilds/ ___________________________________________________ Another online IDE: http://liveworkspace.org/ |
From: Peter K. <syn...@gm...> - 2013-01-19 21:03:07
|
On 19.01.2013 21:26, Ruben Van Boxem wrote: > Hi, > > I have updated the Qt wiki on MinGW-w64: > http://qt-project.org/wiki/MinGW-64-bit > > It has a nice explanation (which was *wrong* on many accounts until now) of various "stuff". > > I'm attempting to build the prereqs now, I might upload them when I succeed. > > Also: it seems the Qt Project chose for "posix" threading for all the wrong reasons in their own release to public > installers, and has no idea of the possible performance impact. It will be positive to get winpthreads and posix > threading out in the wild though :-) Talking about performance, what about a 64bit 4.7.2 release with seh, out of your hands? > > Cheers, > > Ruben > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > > > > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > |
From: Ruben V. B. <van...@gm...> - 2013-01-19 21:05:51
|
2013/1/19 Peter Kümmel <syn...@gm...> > On 19.01.2013 21:26, Ruben Van Boxem wrote: > > Hi, > > > > I have updated the Qt wiki on MinGW-w64: > > http://qt-project.org/wiki/MinGW-64-bit > > > > It has a nice explanation (which was *wrong* on many accounts until now) > of various "stuff". > > > > I'm attempting to build the prereqs now, I might upload them when I > succeed. > > > > Also: it seems the Qt Project chose for "posix" threading for all the > wrong reasons in their own release to public > > installers, and has no idea of the possible performance impact. It will > be positive to get winpthreads and posix > > threading out in the wild though :-) > > Talking about performance, what about a 64bit 4.7.2 release with seh, out > of your hands? > In terms of pure C++ eh stuff, that should be near or better than 32-bit dw2, that is to say, it should show a similar improvement vs 64-bit sjlj as dw2 shows on 32-bit sjlj. If anyone wants to do a short benchmark, I think we'd all be very interested ;-) Ruben > > > > Cheers, > > > > Ruben > > > > > > > ------------------------------------------------------------------------------ > > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > > MVPs and experts. SALE $99.99 this month only -- learn more at: > > http://p.sf.net/sfu/learnmore_122912 > > > > > > > > _______________________________________________ > > Mingw-w64-public mailing list > > Min...@li... > > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > > > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > |
From: Suresh G. <sgo...@ya...> - 2013-01-20 22:14:53
|
On 1/19/2013 12:32 PM, AlexPux wrote: > > Hi, Ruben! > > I also has this work done in my Qt-builds on > https://github.com/Alexpux/Qt-builds. With my scripts > no possible [I think he means: no need to] do full build of > Qt-4.8.4(not tested yet), Qt-5.0.0, Qt-5.0.1 with all Qt > prerequisites and dependencies except Microsoft DirectX SDK. > Binary builds now hosted on > > https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds. Thank you very much for the pre-built packages. It is only in the past few days that I heard of Qt, and have started looking into learning it. My questions: A) Can one go through the "getting started examples" such as qt_quick_app_dev_intro_src.zip, canvasexample_src.zip and notezapp_src.zip (with associated learning guides: QtQuickAppDevIntro.pdf, QtQuickCanvasTutorial.pdf and QtQuickApplicationGuide4Desktop.pdf) found on http://qt-project.org/wiki/developer-guides using AlexPux's prebuilt SDK? B) Also, although I was able to use google to find the pdfs for the above examples, the links on the qt-project.org page for these pdfs are broken. Does the non-functioning of the links to the pdfs mean that these are old examples that might not be applicable to Qt 5.x, and that there are better examples for learning Qt starting with Qt 5.x? By the way, since this thread started with Ruben's post about a wiki page, it might be relevant to note that there are two other "wiki" pages pertaining to Qt and MinGW: http://wiki.batcom-it.net/index.php?title=Building_Qt_on_Windows_(MinGW) http://qt-project.org/wiki/Building_Qt_Desktop_for_Windows_with_MinGW Thanks, --Suresh |
From: K. F. <kfr...@gm...> - 2013-01-21 00:38:45
|
Hi Suresh! On Sun, Jan 20, 2013 at 5:14 PM, Suresh Govindachar <sgo...@ya...> wrote: > ... > Thank you very much for the pre-built packages. It is only in > the past few days that I heard of Qt, and have started looking > into learning it. > > My questions: > ... I can't answer your specific questions, but please let me make two comments: First, I find Qt to be very good. I haven't moved to Qt 5.0 yet, but I have been using Qt 4.8 with mingw-w64 for some time, and, although nothing is perfect, I find that things work quite well. Having said that, Qt does have something of a learning curve, as will any full-featured gui framework, but if you have a need for doing gui development, the time it will take to start learning Qt is time well spent. Second, Qt has an active and very helpful mailing list: "Qt-interest" <int...@qt...> see: http://lists.qt-project.org/mailman/listinfo/interest You should consider subscribing to that list, and asking your Qt-specific questions there. > ... > Thanks, > > --Suresh Happy (Qt) Hacking! K. Frank |
From: Koehne K. <Kai...@di...> - 2013-01-21 09:54:59
|
> -----Original Message----- > From: Suresh Govindachar [mailto:sgo...@ya...] > Sent: Sunday, January 20, 2013 11:15 PM > To: min...@li... > Subject: Re: [Mingw-w64-public] Qt wiki > > [...] > My questions: > > A) Can one go through the "getting started examples" such as > qt_quick_app_dev_intro_src.zip, canvasexample_src.zip and > notezapp_src.zip (with associated learning guides: > QtQuickAppDevIntro.pdf, QtQuickCanvasTutorial.pdf and > QtQuickApplicationGuide4Desktop.pdf) found on > http://qt-project.org/wiki/developer-guides using AlexPux's > prebuilt SDK? > > B) Also, although I was able to use google to find the pdfs for > the above examples, the links on the qt-project.org page for these > pdfs are broken. Does the non-functioning of the links to the > pdfs mean that these are old examples that might not be applicable > to Qt 5.x, and that there are better examples for learning Qt > starting with Qt 5.x? Not sure about the pdf's . What definitely be up to date is the Getting Started guides on http://qt-project.org/doc/qt-5.0/qtdoc/gettingstarted.html Regards Kai |
From: Suresh G. <sgo...@ya...> - 2013-01-20 23:13:00
|
[Sorry, but had to edit the earlier version of this post by adding, for completeness, a link to the wiki page updated by Ruben.] On 1/19/2013 12:32 PM, AlexPux wrote: > > Hi, Ruben! > > I also has this work done in my Qt-builds on > https://github.com/Alexpux/Qt-builds. With my scripts > no possible [I think he means: no need to] do full build of > Qt-4.8.4(not tested yet), Qt-5.0.0, Qt-5.0.1 with all Qt > prerequisites and dependencies except Microsoft DirectX SDK. > Binary builds now hosted on > > https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds. > Thank you very much for the pre-built packages. It is only in the past few days that I heard of Qt, and have started looking into learning it. My questions: A) Can one go through the "getting started examples" such as qt_quick_app_dev_intro_src.zip, canvasexample_src.zip and notezapp_src.zip (with associated learning guides: QtQuickAppDevIntro.pdf, QtQuickCanvasTutorial.pdf and QtQuickApplicationGuide4Desktop.pdf) found on http://qt-project.org/wiki/developer-guides using AlexPux's prebuilt SDK? B) Also, although I was able to use google to find the pdfs for the above examples, the links on the qt-project.org page for these pdfs are broken. Does the non-functioning of the links to the pdfs mean that these are old examples that might not be applicable to Qt 5.x, and that there are better examples for learning Qt starting with Qt 5.x? By the way, since this thread started with Ruben's post about the wiki page he updated: http://qt-project.org/wiki/MinGW-64-bit it might be relevant to note that there are two other "wiki" pages pertaining to Qt and MinGW: http://wiki.batcom-it.net/index.php?title=Building_Qt_on_Windows_(MinGW) http://qt-project.org/wiki/Building_Qt_Desktop_for_Windows_with_MinGW Thanks, --Suresh |
From: Алексей П. <al...@gm...> - 2013-01-21 05:31:52
|
> > By the way, since this thread started with Ruben's post about > the wiki page he updated: > > http://qt-project.org/wiki/MinGW-64-bit > > This wiki for building Qt-5.x. > it might be relevant to note that there are two other "wiki" > pages pertaining to Qt and MinGW: > > http://wiki.batcom-it.net/index.php?title=Building_Qt_on_Windows_(MinGW) > http://qt-project.org/wiki/Building_Qt_Desktop_for_Windows_with_MinGW > > And this for Qt-4.x. |
From: Koehne K. <Kai...@di...> - 2013-01-21 08:30:06
|
> -----Original Message----- > From: Ruben Van Boxem [mailto:van...@gm...] > Sent: Saturday, January 19, 2013 9:27 PM > To: min...@li... > Subject: [Mingw-w64-public] Qt wiki > > Hi, Hi Ruben & others, Thanks for the fixes to the wiki! > I have updated the Qt wiki on MinGW-w64: > http://qt-project.org/wiki/MinGW-64-bit > > > It has a nice explanation (which was *wrong* on many accounts until now) of > various "stuff". > > I'm attempting to build the prereqs now, I might upload them when I > succeed. Actually all that should be needed for latest qt5/release branch (upcoming 5.0.1) is the toolchain + ICU and openssl dlls, which you can get e.g. from http://origin.releases.qt-project.org/prebuilt/mingw_32/ . > > Also: it seems the Qt Project chose for "posix" threading for all the wrong > reasons in their own release to public installers, and has no idea of the > possible performance impact. It will be positive to get winpthreads and posix > threading out in the wild though :-) The section of posix vs win32 threading was just what I found out on the web after googling for 10 minutes ;) We just had to settle for one. If there's consensus that win32 threading is preferred by more people we can switch to it e.g. for Qt 5.1 ... Regards Kai |
From: Ruben V. B. <van...@gm...> - 2013-01-21 08:48:04
|
2013/1/21 Koehne Kai <Kai...@di...> > > > -----Original Message----- > > From: Ruben Van Boxem [mailto:van...@gm...] > > Sent: Saturday, January 19, 2013 9:27 PM > > To: min...@li... > > Subject: [Mingw-w64-public] Qt wiki > > > > Hi, > > Hi Ruben & others, > > Thanks for the fixes to the wiki! > > > I have updated the Qt wiki on MinGW-w64: > > http://qt-project.org/wiki/MinGW-64-bit > > > > > > It has a nice explanation (which was *wrong* on many accounts until now) > of > > various "stuff". > > > > I'm attempting to build the prereqs now, I might upload them when I > > succeed. > > Actually all that should be needed for latest qt5/release branch (upcoming > 5.0.1) is the toolchain + ICU and openssl dlls, which you can get e.g. from > http://origin.releases.qt-project.org/prebuilt/mingw_32/ . > > > > > Also: it seems the Qt Project chose for "posix" threading for all the > wrong > > reasons in their own release to public installers, and has no idea of the > > possible performance impact. It will be positive to get winpthreads and > posix > > threading out in the wild though :-) > > The section of posix vs win32 threading was just what I found out on the > web after googling for 10 minutes ;) We just had to settle for one. If > there's consensus that win32 threading is preferred by more people we can > switch to it e.g. for Qt 5.1 ... > Well, it's kind of a double-edged blade as I tried to clarify on the wiki. Support is still experimental, but that won't change if there's no exposure of this build to the masses. On top of that, Qt already caters for all the C++11 multithreading classes: QThread, QMutex, etc... all exist and are probably the ones used in Qt projects. I'll leave the final decision up to you, but for stability's sake I'd suggest using plain win32 threading (Qt is used by a lot of people and it'd suck for people to have a bad MinGW-w64 experience with it). Perhaps ktietz (the winpthreads author) can chime in on this. Ruben > Regards > > Kai > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122412 > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > |
From: Koehne K. <Kai...@di...> - 2013-01-21 08:49:45
|
> -----Original Message----- > From: Koehne Kai [mailto:Kai...@di...] > Sent: Monday, January 21, 2013 9:30 AM > To: min...@li... > Subject: Re: [Mingw-w64-public] Qt wiki > > > > Actually all that should be needed for latest qt5/release branch (upcoming > 5.0.1) is the toolchain + ICU and openssl dlls, which you can get e.g. from > http://origin.releases.qt-project.org/prebuilt/mingw_32/ . Alright, I guess I forgot to mention Python, Perl, Ruby + ICU and OpenSSL headers , and optionally the DirectX SDK :) The point I was trying to make was: You shouldn't need any patches for Qt itself anymore. Regards Kai |
From: Алексей П. <al...@gm...> - 2013-01-21 08:54:41
|
Hi, Kai! Does the issue reported on https://bugreports.qt-project.org/browse/QTBUG-28845 is closed? And I have one patch that not in release branch yet: --- a/qtwebkit/Tools/qmake/mkspecs/features/default_pre.prf.orig 2013-01-11 14:18:00 +0300 +++ b/qtwebkit/Tools/qmake/mkspecs/features/default_pre.prf 2013-01-11 14:18:07 +0300 @@ -21,6 +21,9 @@ WEBKIT_SUBDIR = $$replace(_PRO_FILE_PWD_, $${ROOT_WEBKIT_DIR},) ROOT_BUILD_DIR = $$replace(OUT_PWD, $${WEBKIT_SUBDIR}$,) +# Make sure we process the PKGCONFIG variable if applicable +!mac: CONFIG += link_pkgconfig + # Now we're ready to load default_pre from Qt load(default_pre) 2013/1/21 Koehne Kai <Kai...@di...> > > > > -----Original Message----- > > From: Koehne Kai [mailto:Kai...@di...] > > Sent: Monday, January 21, 2013 9:30 AM > > To: min...@li... > > Subject: Re: [Mingw-w64-public] Qt wiki > > > > > > > > Actually all that should be needed for latest qt5/release branch > (upcoming > > 5.0.1) is the toolchain + ICU and openssl dlls, which you can get e.g. > from > > http://origin.releases.qt-project.org/prebuilt/mingw_32/ . > > Alright, I guess I forgot to mention Python, Perl, Ruby + ICU and OpenSSL > headers , and optionally the DirectX SDK :) > > The point I was trying to make was: You shouldn't need any patches for Qt > itself anymore. > > Regards > > Kai > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122412 > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > |
From: Koehne K. <Kai...@di...> - 2013-01-21 09:12:23
|
> -----Original Message----- > From: Алексей Павлов [mailto:al...@gm...] > Sent: Monday, January 21, 2013 9:55 AM > To: min...@li... > Subject: Re: [Mingw-w64-public] Qt wiki > > Hi, Kai! > Does the issue reported on https://bugreports.qt- > project.org/browse/QTBUG-28845 is closed? Well, technically it's still 'not evaluated' :) I never had that problem personally before, nor did it occur in the CI system. But then again I'm using jom, maybe it's a jom vs mingw32-make difference ... will try later on with mingw32-make. > And I have one patch that not in release branch yet: > > --- a/qtwebkit/Tools/qmake/mkspecs/features/default_pre.prf.orig 2013- > 01-11 14:18:00 +0300 > +++ b/qtwebkit/Tools/qmake/mkspecs/features/default_pre.prf 2013-01-11 > +++ 14:18:07 +0300 > @@ -21,6 +21,9 @@ > WEBKIT_SUBDIR = $$replace(_PRO_FILE_PWD_, $${ROOT_WEBKIT_DIR},) > ROOT_BUILD_DIR = $$replace(OUT_PWD, $${WEBKIT_SUBDIR}$,) > > +# Make sure we process the PKGCONFIG variable if applicable > +!mac: CONFIG += link_pkgconfig > + > # Now we're ready to load default_pre from Qt > load(default_pre) Can you elaborate what that fixes + is there a bugreport for it? Note that we're pretty near the 5.0.1 release (which will include pre-built MinGW packages + Mingw-builds toolchain), so if we want still something fixed we've to hurry up ... Regards Kai |
From: Алексей П. <al...@gm...> - 2013-01-21 09:21:00
|
2013/1/21 Koehne Kai <Kai...@di...> > > > > And I have one patch that not in release branch yet: > > > > --- a/qtwebkit/Tools/qmake/mkspecs/features/default_pre.prf.orig 2013- > > 01-11 14:18:00 +0300 > > +++ b/qtwebkit/Tools/qmake/mkspecs/features/default_pre.prf 2013-01-11 > > +++ 14:18:07 +0300 > > @@ -21,6 +21,9 @@ > > WEBKIT_SUBDIR = $$replace(_PRO_FILE_PWD_, $${ROOT_WEBKIT_DIR},) > > ROOT_BUILD_DIR = $$replace(OUT_PWD, $${WEBKIT_SUBDIR}$,) > > > > +# Make sure we process the PKGCONFIG variable if applicable > > +!mac: CONFIG += link_pkgconfig > > + > > # Now we're ready to load default_pre from Qt > > load(default_pre) > > Can you elaborate what that fixes + is there a bugreport for it? Note that > we're pretty near the 5.0.1 release (which will include pre-built MinGW > packages + Mingw-builds toolchain), so if we want still something fixed > we've to hurry up ... Jonathan Liu <ne...@gm...> write bugreport for it on https://bugs.webkit.org/show_bug.cgi?id=106647 and patch is committed to upstream |
From: niXman <i.n...@gm...> - 2013-01-21 14:27:35
|
> On top of that, Qt already caters for all the C++11 multithreading classes: > QThread, QMutex, etc... all exist and are probably the ones used in Qt > projects. I'll leave the final decision up to you, but for stability's sake > I'd suggest using plain win32 threading (Qt is used by a lot of people and > it'd suck for people to have a bad MinGW-w64 experience with it). You say this as if those who use Qt, do not use C++11 and its 'threading support'. I know that winpthreads has some bugs, иut this does not mean that you can not use winpthreads. The less MinGW users will use builds with winpthreads, the fewer bugs will be found and even fewer corrected. If your words said above serve to this purpose, I...hmmm...better say nothing.. =) Kai, I would not recommend to use win32-threads builds, because so the full support for 'C++11 threads support library' will appear only after several years. About the current support for 'C++11 threads support library' in MinGW we can not say that it does not exist or it is not working. It exists, and it works. And I think it works quite well. P.S. the discussed above was about the overhead created by winpthreads. on my own behalf, I would say that this overhead is so insignificant that it is ridiculous to discuss it =) -- Regards, niXman ___________________________________________________ Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows: http://sourceforge.net/projects/mingwbuilds/ ___________________________________________________ Another online IDE: http://liveworkspace.org/ |
From: K. F. <kfr...@gm...> - 2013-01-21 14:50:23
|
Hello niXman! I agree with what you are saying. On Mon, Jan 21, 2013 at 9:27 AM, niXman <i.n...@gm...> wrote: >> On top of that, Qt already caters for all the C++11 multithreading classes: >> QThread, QMutex, etc... all exist and are probably the ones used in Qt >> projects. I'll leave the final decision up to you, but for stability's sake >> I'd suggest using plain win32 threading (Qt is used by a lot of people and >> it'd suck for people to have a bad MinGW-w64 experience with it). > > You say this as if those who use Qt, do not use C++11 and its > 'threading support'. > I know that winpthreads has some bugs, иut this does not mean that you > can not use winpthreads. The less MinGW users will use builds with > winpthreads, the fewer bugs will be found and even fewer corrected. If > your words said above serve to this purpose, I...hmmm...better say > nothing.. =) >From my perspective, I want to use c++11 / std::thread with Qt, and I am, using Ruben's std::thread > Kai, I would not recommend to use win32-threads builds, because so the > full support for 'C++11 threads support library' will appear only > after several years. > About the current support for 'C++11 threads support library' in MinGW > we can not say that it does not exist or it is not working. It exists, > and it works. And I think it works quite well. I have not succeeded in breaking mingw-w64's std::thread (based on winpthreads) support. I have run basic tests that cover all of the standard facilities (mutexes, condition variables, joins, futures, throwing exceptions across futures). I'm not saying it's perfect or has no bugs, but I haven't found any yet. > P.S. > the discussed above was about the overhead created by winpthreads. > on my own behalf, I would say that this overhead is so insignificant > that it is ridiculous to discuss it =) >From the std::thread perspective, I have identified some overhead caused by implementing std::thread on top of winpthreads relative to implementing it directly on top of win32, but it is not excessive. Also, Kai's winpthreads implementation also outperforms certain facets of the native implementation. Obviously giving users a "broken" Qt / mingw-w64 experience because of winpthreads would be a bad idea. But it works for me. And I agree with niXman that if things are working reasonably well (I think they are.), then encouraging people to go the winpthreads route will only server to strengthen winpthreads. > Regards, > niXman Best. Frank R. Brown |
From: Koehne K. <Kai...@di...> - 2013-01-22 07:53:06
|
Hi guys, Thanks for the lively discussion! In the end we (Qt 5.0.1 release team) decided to stick with the 'posix' (libwinpthread) toolchain: There's obviously no consensus what do use in the community here, and I personally don't have enough insight to make a really 'informed' decision. If we get bug reports etc there's still the option to switch in later versions ... Regards Kai PS: I think it would be help adaptation of the project a lot if things like posix vs win32 threading, and sjlj vs dw2 exception handling (preferably even with an advice what to use by default) would be documented somewhere within the mingw-w64 project site. > -----Original Message----- > From: K. Frank [mailto:kfr...@gm...] > Sent: Monday, January 21, 2013 3:50 PM > To: min...@li... > Subject: Re: [Mingw-w64-public] Qt wiki > > Hello niXman! > > I agree with what you are saying. > > On Mon, Jan 21, 2013 at 9:27 AM, niXman <i.n...@gm...> wrote: > >> On top of that, Qt already caters for all the C++11 multithreading classes: > >> QThread, QMutex, etc... all exist and are probably the ones used in > >> Qt projects. I'll leave the final decision up to you, but for > >> stability's sake I'd suggest using plain win32 threading (Qt is used > >> by a lot of people and it'd suck for people to have a bad MinGW-w64 > experience with it). > > > > You say this as if those who use Qt, do not use C++11 and its > > 'threading support'. > > I know that winpthreads has some bugs, иut this does not mean that you > > can not use winpthreads. The less MinGW users will use builds with > > winpthreads, the fewer bugs will be found and even fewer corrected. If > > your words said above serve to this purpose, I...hmmm...better say > > nothing.. =) > > From my perspective, I want to use c++11 / std::thread with Qt, and I am, > using Ruben's std::thread > > > Kai, I would not recommend to use win32-threads builds, because so the > > full support for 'C++11 threads support library' will appear only > > after several years. > > About the current support for 'C++11 threads support library' in MinGW > > we can not say that it does not exist or it is not working. It exists, > > and it works. And I think it works quite well. > > I have not succeeded in breaking mingw-w64's std::thread (based on > winpthreads) support. I have run basic tests that cover all of the standard > facilities (mutexes, condition variables, joins, futures, throwing exceptions > across futures). I'm not saying it's perfect or has no bugs, but I haven't found > any yet. > > > P.S. > > the discussed above was about the overhead created by winpthreads. > > on my own behalf, I would say that this overhead is so insignificant > > that it is ridiculous to discuss it =) > > From the std::thread perspective, I have identified some overhead caused > by implementing std::thread on top of winpthreads relative to implementing > it directly on top of win32, but it is not excessive. > Also, Kai's winpthreads implementation also outperforms certain facets of > the native implementation. > > Obviously giving users a "broken" Qt / mingw-w64 experience because of > winpthreads would be a bad idea. But it works for me. And I agree with > niXman that if things are working reasonably well (I think they are.), then > encouraging people to go the winpthreads route will only server to > strengthen winpthreads. > > > Regards, > > niXman > > > Best. > > > Frank R. Brown > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, > Windows 8 Apps, JavaScript and much more. Keep your skills current with > LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and > experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122412 > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public |
From: NightStrike <nig...@gm...> - 2013-02-14 15:52:11
|
On Mon, Jan 21, 2013 at 9:52 PM, Koehne Kai <Kai...@di...> wrote: > PS: I think it would be help adaptation of the project a lot if things like posix vs win32 threading, and sjlj vs dw2 exception handling (preferably even with an advice what to use by default) would be documented somewhere within the mingw-w64 project site. Feel free to add this to the wiki. |