On Wednesday 17 December 2014 11:55:21 René J.V. Bertin wrote:
QIcon() isn't inline and neither is it marked as noexcept. Therefore, the
compiler must add surrounding EH code so that any locals you have in the
context where that QIcon was created can be destructed.
And QIcon() is part of
On Tuesday 16 December 2014 17:37:02 René J.V. Bertin wrote:
Out of curiosity, what does building with -fexceptions (= without
-fno-exceptions) do to simple calls like QString() or QIcon()? Does it
introduce overhead there?
Yes and no. QString() is inline, so the compiler can tell that it
On Thursday December 11 2014 15:25:55 Thiago Macieira wrote:
On Thursday 11 December 2014 21:33:35 René J.V. Bertin wrote:
But how do I turn exceptions back on in xmlpatterns.pro? Do I add
-UQT_NO_EXCEPTIONS to the compiler flags (and cross thumbs), or is there a
better way?
CONFIG +=
On Friday 12 December 2014 12:49:17 René J.V. Bertin wrote:
On Thursday December 11 2014 15:25:55 Thiago Macieira wrote:
On Thursday 11 December 2014 21:33:35 René J.V. Bertin wrote:
But how do I turn exceptions back on in xmlpatterns.pro? Do I add
-UQT_NO_EXCEPTIONS to the compiler flags
On Friday 12 December 2014 18:49:44 René J.V. Bertin wrote:
On Friday December 12 2014 09:14:52 Thiago Macieira wrote:
Right. QtConcurrent doesn't need it, but it does offer support for catching
an exception in a thread and rethrowing it in the future's thread. In Qt
4, it is in QtCore.
And
On Wednesday December 10 2014 18:03:15 Thiago Macieira wrote:
That's what I saw after reading up a bit more on the topic. But if
QtXmlPatterns doesn't build without them, I'm stuck with -fexceptions as
KDE uses QtXmlPatterns ...
Try and see. I think xmlpatterns.pro turns it back on, but
On Thursday 11 December 2014 18:44:38 René J.V. Bertin wrote:
On Wednesday December 10 2014 18:03:15 Thiago Macieira wrote:
That's what I saw after reading up a bit more on the topic. But if
QtXmlPatterns doesn't build without them, I'm stuck with -fexceptions as
KDE uses QtXmlPatterns
On Thursday December 11 2014 09:49:35 Thiago Macieira wrote:
Use Qt 5. It's done there.
How funny
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On Thursday 11 December 2014 19:31:32 René J.V. Bertin wrote:
On Thursday December 11 2014 09:49:35 Thiago Macieira wrote:
Use Qt 5. It's done there.
How funny
Edit configure so it won't disable qtxmlpatterns. Then edit
src/xmlpatterns/xmlpatterns.pro to turn exceptions back on.
--
On Thursday December 11 2014 10:52:00 Thiago Macieira wrote:
Edit configure so it won't disable qtxmlpatterns. Then edit
src/xmlpatterns/xmlpatterns.pro to turn exceptions back on.
The configure edit seems easy enough: just change the block
if [ $CFG_XMLPATTERNS = yes -a $CFG_EXCEPTIONS = no
On Thursday December 11 2014 10:52:00 Thiago Macieira wrote:
src/xmlpatterns/xmlpatterns.pro to turn exceptions back on.
Doh...
DEFINES-=QT_NO_EXCEPTIONS should do the trick (with that, no sign of anything
exception in src/xmlpatterns/Makefile)
R.
On Thursday 11 December 2014 21:33:35 René J.V. Bertin wrote:
But how do I turn exceptions back on in xmlpatterns.pro? Do I add
-UQT_NO_EXCEPTIONS to the compiler flags (and cross thumbs), or is there a
better way?
CONFIG += exceptions
--
Thiago Macieira - thiago.macieira (AT) intel.com
On Wednesday 10 December 2014 14:24:03 René J.V. Bertin wrote:
Hello,
After configuring Qt 4.8.6 without any specific options, a message is
printed suggesting that one may want to re-run the process passing
-fno-exceptions to the compiler, in order to reduce memory usage (and I
suppose some
On Wednesday 10 December 2014 20:38:20 René J.V. Bertin wrote:
Set the flag. I'm not sure if you'll have problems with QtXmlPatterns, but
I don't think you will.
That's what I saw after reading up a bit more on the topic. But if
QtXmlPatterns doesn't build without them, I'm stuck with
14 matches
Mail list logo
