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
Hello niXman!
I agree with what you are saying.
On Mon, Jan 21, 2013 at 9:27 AM, niXman 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
> 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 peop
2013/1/21 Jacek Caban :
> On 01/21/13 13:39, JonY wrote:
>> On 1/21/2013 09:43, Herb Thompson wrote:
>>> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
>>> could not be located in the dynamic link library msvcrt.dll' on Windows
>>> XP SP1?
>>>
>>> A: For C++, MinGW-w64 imple
On 01/21/13 13:39, JonY wrote:
> On 1/21/2013 09:43, Herb Thompson wrote:
>> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
>> could not be located in the dynamic link library msvcrt.dll' on Windows
>> XP SP1?
>>
>> A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__s
On 1/21/2013 09:43, Herb Thompson wrote:
> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
> could not be located in the dynamic link library msvcrt.dll' on Windows
> XP SP1?
>
> A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__stream, const
> wchar_t *__format, __
> -Original Message-
> From: Suresh Govindachar [mailto:sgovindac...@yahoo.com]
> Sent: Sunday, January 20, 2013 11:15 PM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] Qt wiki
>
> [...]
>My questions:
>
>A) Can one go through the "getting started
2013/1/21 Koehne Kai
>
>
> > 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
> -Original Message-
> From: Алексей Павлов [mailto:alex...@gmail.com]
> Sent: Monday, January 21, 2013 9:55 AM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] Qt wiki
>
> Hi, Kai!
> Does the issue reported on https://bugreports.qt-
> project.org/browse/QTB
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_pr
> -Original Message-
> From: Koehne Kai [mailto:kai.koe...@digia.com]
> Sent: Monday, January 21, 2013 9:30 AM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: Re: [Mingw-w64-public] Qt wiki
>
>
>
> Actually all that should be needed for latest qt5/release branch (upcoming
> 5.0
2013/1/21 Koehne Kai
>
> > -Original Message-
> > From: Ruben Van Boxem [mailto:vanboxem.ru...@gmail.com]
> > Sent: Saturday, January 19, 2013 9:27 PM
> > To: mingw-w64-public@lists.sourceforge.net
> > Subject: [Mingw-w64-public] Qt wiki
> >
> > Hi,
>
> Hi Ruben & others,
>
> Thanks for t
> -Original Message-
> From: Ruben Van Boxem [mailto:vanboxem.ru...@gmail.com]
> Sent: Saturday, January 19, 2013 9:27 PM
> To: mingw-w64-public@lists.sourceforge.net
> Subject: [Mingw-w64-public] Qt wiki
>
> Hi,
Hi Ruben & others,
Thanks for the fixes to the wiki!
> I have updated th
13 matches
Mail list logo