Thank you. That was it...
Btw, the Qt deploy tool did not package th s
--Scott
Original message
From: Hamish Moffatt ham...@risingsoftware.com
Date:03/03/2015 20:13 (GMT-08:00)
To: interest@qt-project.org
Cc:
Subject: Re: [Interest] Printing not working on Windows
On
On Wednesday 04 March 2015 13:36:14 Sorvig Morten wrote:
ARC: Qt does not use ARC because it's not supported for 32-bit builds. It’s
not supported on 10.6 either, which is why the topic was brought up when we
dropped support for 10.6.
If we don't use ARC, why did we drop 10.6?
--
Thiago
On Wednesday March 04 2015 13:20:08 Becsi Andras wrote:
Hi,
I can only repeat myself: out-of-tree build of QtWebEngine is not supported
with 5.4.x (it is only supported with -developer-build).
That's not really the kind of answer I expect to a why question ;)
This has been fixed in 5.5, and
On Wednesday 04 March 2015 17:15:45 Scott Aron Bloom wrote:
By then its too late.. I want the shell script that calls the make system to
fail, saying you have the qmake setup wrong...
Why would it be wrong? If qmake is installed, it's been installed correctly
right? :-)
And what is the issue
On 4 March 2015 at 18:05, Scott Aron Bloom scott.bl...@onshorecs.com wrote:
I am creating two versions of my tool, 32 and 64 bit. However, I have, more
than once, started a build against the wrong path, so it was building
against Qt 64 when it was supposed to build against Qt 32 (or vice
On 4 March 2015 at 12:43, Matthias Thöny tho...@gmail.com wrote:
I don't really see the proposed work around. Because you cannot actually
call any QT function based on OpenGL 3.0 anymore without letting the
application crash (e.g. renderText in QGLWindow) , when selecting a 4.1
context (only
If you are trying to figure out which qmake created the Makefile your
script is using, you can try call make qmake -n. This will give you the
qmake command that is being used including the path to qmake itself. You
can then query that qmake for the QMAKE_SPEC it is defaults to
(linux-g++-64 or
Hi,
Please let me know if there is any QML Equivalent of QCustomplot for plotting
and data visualization?
Thanks and Regards,
Ramakanth
Disclaimer: This message
Am 04.03.2015 um 12:49 schrieb Thiago Macieira thiago.macie...@intel.com:
On Wednesday 04 March 2015 13:36:14 Sorvig Morten wrote:
ARC: Qt does not use ARC because it's not supported for 32-bit builds. It’s
not supported on 10.6 either, which is why the topic was brought up when we
dropped
Provided you defined a mkspec when you built Qt, you can put something like
this in your project file:
linux-g++-64{
message(Building for linux 64-bit)
LIBS += -lusb -L../lib64
}
linux-g++-32{
message(Building for linux 32-bit)
LIBS += -L../lib
}
win32-g++{
message(Building for windows 32-bit)
On Mar 4, 2015, at 11:44 AM, Thiago Macieira thiago.macie...@intel.com
wrote:
On Wednesday 04 March 2015 17:15:45 Scott Aron Bloom wrote:
By then its too late.. I want the shell script that calls the make system to
fail, saying you have the qmake setup wrong...
Why would it be wrong?
I am creating two versions of my tool, 32 and 64 bit. However, I have, more
than once, started a build against the wrong path, so it was building against
Qt 64 when it was supposed to build against Qt 32 (or vice versa)
Is there a qmake or some way, that in the setup scripts to my build, I can
This does not prevent applications from using ARC since it can be enabled per
translation unit. We would like to start using ARC internally in Qt as well,
but the requirement to drop 32-bit support may be too steep at this point in
time. (Question for interest@: is 32-bit support
-Original Message-
From: interest-bounces+scott.bloom=onshorecs@qt-project.org
[mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On Behalf Of
Thiago Macieira
Sent: Wednesday, March 04, 2015 9:44 AM
To: interest@qt-project.org
Subject: Re: [Interest] Is there a
On Wednesday March 04 2015 13:57:11 Till Oliver Knoll wrote:
If we don't use ARC, why did we drop 10.6?
Could C++11 support be a reason? 10.6 doesn't have that (with the default
Apple provided compiler).
I cannot speak for 32bit builds, but I think the real issue is with building.
10.7
font.weight
Von: interest-bounces+alessandro.portale=theqtcompany@qt-project.org
interest-bounces+alessandro.portale=theqtcompany@qt-project.org im
Auftrag von Alexander Ivash elder...@gmail.com
Gesendet: Dienstag, 3. März 2015 19:45
An:
On 01/03/15 20:57, Thiago Macieira wrote:
On Sunday 01 March 2015 10:30:22 Nikos Chantziaras wrote:
On 28/02/15 21:15, Thiago Macieira wrote:
On Saturday 28 February 2015 14:01:33 Nikos Chantziaras wrote:
But when building for Windows, this doesn't work:
qmake CONFIG+=debug
make
On Wednesday 04 March 2015 18:39:55 Scott Aron Bloom wrote:
No. Maybe Im not explaining myself correctly. Since this was purely a
question on qmake, or if there was anyway to look at a Qt install an see
what bit width it was built against.
However here are all the gory details.
On a
[re missing windowsprintersupport.dll]
On 05/03/15 02:45, Scott Aron Bloom wrote:
Thank you. That was it...
Btw, the Qt deploy tool did not package th s
The deploy tools can't tell what plugins you need. macdeployqt seems to
err on the side of copying everything; I haven't used
Thank you, but unfortunately such approach disallows changing stroke
thickness independently of font itself. I'd like to keep font 'normal' and
get 5 pixel stroke around it.
2015-03-04 18:54 GMT+03:00 Portale Alessandro
alessandro.port...@theqtcompany.com:
font.weight
I think qttools has a dependency on webkit, because if I configure with
-no-icu, or if I am doing an Android build, then qttools never gets built
automatically, and I have to do it manually. (It would be the same if some of
webkit’s extra dependencies are not in place.) The reason is that
On Tuesday March 03 2015 17:13:51 Thiago Macieira wrote:
any Qt version built from sources a developer build?
He means a build done using the configure switch -developer-build.
Ah, of course. I know I want to stay away from that switch ...
The question remains: why do I get a qmake error on
Looks like Thiago is mis-remembering some of the discussion here, I’ll try to
clear things up a bit. The following should apply to all of Qt, with the
exception of QtWebKit and QtWebEngine which follow the rules set by the
upstream projects.
GC: Qt does not use the Cocoa garbage collector, and
Hi,
On 04 Mar 2015, at 10:11 , René J.V. Bertin
rjvber...@gmail.commailto:rjvber...@gmail.com wrote:
On Tuesday March 03 2015 17:13:51 Thiago Macieira wrote:
any Qt version built from sources a developer build?
He means a build done using the configure switch -developer-build.
Ah, of course.
On Tuesday March 03 2015 19:34:45 Thiago Macieira wrote:
No. It really seems that ARC is only supported for 64 bit binaries, see e.g.
here:
I haven't heard anything about 32-bit support
Apple's own documentation seems to suggest that 32bit ARC was not available on
10.6, implying that it *is*
On Wed, Mar 4, 2015 at 5:36 AM, Sorvig Morten
morten.sor...@theqtcompany.com wrote:
This does not prevent applications from using ARC since it can be enabled
per translation unit. We would like to start using ARC internally in Qt as
well, but the requirement to drop 32-bit support may be too
26 matches
Mail list logo
