On sexta-feira, 24 de agosto de 2012 13.51.29, Loaden wrote:
> There exist better way to solved the problem?
> Please point out.
>
> Thanks a lot!
By the way, please use the releas...@qt-project.org mailing list for
discussing the status of the beta packages. And please include the date of the
pac
For now user can add build_all in qconfig.pri / CONFIG on Windows
Change From: CONFIG += debug ... To: CONFIG += debug build_all ...
And using -debug-and-release config option.
It will build and install debug target first,
then build and install release target.
It make sure all execute files be r
Still now work!
2012/8/23 Loaden
> change the install root path from d:\qpSOFT\Projects\BuildQt5-m64\temp
> to d:/qpSOFT/Projects/BuildQt5-m64/temp ?
>
--
Best Regards
Yuchen
___
Development mailing list
Development@qt-project.org
http://lists.qt-p
On Aug 23, 2012, at 4:33 PM, ext Laszlo Papp
mailto:lp...@kde.org>> wrote:
Hi Gunnar,
Thank you for your explanation.
I have a question and a comment about the procedure in general:
1) Self-approval accepted from a Maintainer for a playground project? The
description here does not mention th
On Aug 23, 2012, at 1:58 PM, ext Oswald Buddenhagen
wrote:
> On Thu, Aug 23, 2012 at 07:30:23AM +, ext casper.vandonde...@nokia.com
> wrote:
>> example:
>> /*!
>>\class QObject
>>\inmodule QtCore
>> ...
>> */
>>
> isn't it a *tad* weird that sources in a modularized package need t
Here are the partial results for Windows:
https://docs.google.com/spreadsheet/pub?key
vVqQ9a3_pIudExQek1hOXRyTVVZZ0tMN1kzQjdhNGc&gid=1
Just like on Linux, the new QMutex is much worse than native and than Qt 4.8
for the contended case. Both contention cases are showing 700% worse than
Windows nati
Hi,
We have recieved some feedback that the descriptions on how to install Qt 5
(the readme-file and http://qt-project.org/wiki/Building_Qt_5_from_Git) needs
updating.
Christian Strømme has volunteered to take care of the Linux version. We need
someone to help with Mac and Windows.
Please let
Hi all,
In case you know that bug is a blocker for Qt 5 beta release could you please
add "Fix Versioin/s: 5.0.0 Beta 1" when reporting bug?
Also link (More Actions - Link - Is required for) those tasks to task:
https://bugreports.qt-project.org/browse/QTBUG-26922
That will ease significantly
Hi Gunnar,
Thank you for your explanation.
I have a question and a comment about the procedure in general:
1) Self-approval accepted from a Maintainer for a playground project? The
description here does not mention that, and I am unsure what the default
is. :-)
http://qt-project.org/wiki/Creati
Hi everyone,
As you probably know we are working to release Qt 5 beta, and a lot of people
are helping with the testing.
Here is a list of the most critical issues we know about so far:
https://bugreports.qt-project.org/browse/QTBUG-26959
https://bugreports.qt-project.org/browse/QTBUG-26943
http
Hello
I'd like to offer the a clarification and request one change to the commit
policy regarding the maintainer's privilege. See
http://qt-project.org/wiki/Commit_Policy (point 12)
http://lists.qt-project.org/pipermail/development/2012-April/002930.html
The policy says:
12.1 Main
Do you mean I need change the install root path from
d:\qpSOFT\Projects\BuildQt5-m64\temp
to d:/qpSOFT/Projects/BuildQt5-m64/temp ?
2012/8/23 Oswald Buddenhagen
> d:\qpSOFT\Projects\BuildQt5-m64\temp/
>
--
Best Regards
Yuchen
___
Development maili
On terça-feira, 21 de agosto de 2012 22.36.38, Thiago Macieira wrote:
> I've just done some benchmarking of QMutex on Linux, using the pthread
> implementation instead of the futex one.
Collated in a spreadsheet:
https://docs.google.com/spreadsheet/pub?key
vVqQ9a3_pIudExQek1hOXRyTVVZZ0tMN1kzQjdhN
On Thu, Aug 23, 2012 at 06:40:56PM +0800, ext Loaden wrote:
> *mingw32-make --trace install INSTALL_ROOT=%INSTROOT% >>install.log 2>&1*
> Error MSG:
>
> > if not exist
> > d:\qpSOFT\Projects\BuildQt5-m64\temp/qpSOFT/Projects/BuildQt5-m64/qtbase/lib/pkgconfig
> > mkdir
> > d:\qpSOFT\Projects\BuildQ
On Thu, Aug 23, 2012 at 07:30:23AM +, ext casper.vandonde...@nokia.com
wrote:
> example:
> /*!
> \class QObject
> \inmodule QtCore
> ...
> */
>
isn't it a *tad* weird that sources in a modularized package need to
declare in which package they are, several hundred times? i call that
"s
On quarta-feira, 22 de agosto de 2012 13.21.03, bradley.hug...@nokia.com
wrote:
> Wow… do you get the same results with Qt 4? I did quite a bit to optimize
> contention performance in Qt 4. I do know that mutex contention performance
> has regressed in Qt 5 on the Mac, I wasn't sure about on Linux,
*mingw32-make --trace install INSTALL_ROOT=%INSTROOT% >>install.log 2>&1*
Error MSG:
> makefile:56: update target `module-qtbase-install_subtargets' due to: FORCE
> if not exist qtbase\ mkdir qtbase\
> cd qtbase\ && ( if not exist Makefile
> d:\qpSOFT\Projects\BuildQt5-m64\qtbase\bin\qmake
> d:\qp
On quinta-feira, 23 de agosto de 2012 12.10.35, Thiago Macieira wrote:
> On quinta-feira, 23 de agosto de 2012 07.30.23, casper.vandonde...@nokia.com
> wrote:
> > What needs to be done:
> > - Find the qdoc comment containing \class in your classes.
> > - Add a new line containing the text "\inmodul
On quinta-feira, 23 de agosto de 2012 07.30.23, casper.vandonde...@nokia.com
wrote:
> What needs to be done:
> - Find the qdoc comment containing \class in your classes.
> - Add a new line containing the text "\inmodule [modulename]"
> - Do this for each of the classes, that does not have an \inmod
On quinta-feira, 23 de agosto de 2012 01.40.00, Holger Hans Peter Freyther >
In fact in Yocto/Poky we are using a custom mkspec that allows us to target
> 7 different CPU architectures. I would be very happy if Qt would use
> autoconf (and pkg-config) for the configuration step on Unix/Posix (it
>
Hi,
To be able to properly generate modularized Qt documentation we need QDoc to
know in which module a class resides and I need help with this if we want to
get modularization (mostly) done before the Qt 5 release.
Previously QDoc would guess to which module a class belonged by finding
keywor
21 matches
Mail list logo
