Hi,
I've got Qt iOS application and wanted to add watchOS part, but got a
problem compiling Qt with bitcode enabled, which is the requirement. That's
why I downloaded latest source of Qt5.8 and tried to compile it on my own
but coma across some problems.
I got newest Xcode 8(maybe that's the prob
Actually you can vote for it and promote to other users to vote for it.
More votes - more chances issue to be solved
On Wed, Sep 21, 2016 at 2:51 PM, Jason H wrote:
> This gets at what I don't like about Qt the most: As a user I have no
> control of where it goes. I can (and do) file bugs and fe
Den 21-09-2016 kl. 23:53 skrev André Pönitz:
On Wed, Sep 21, 2016 at 05:42:44AM +, Shawn Rutledge wrote:
On Sep 20, 2016, at 22:52, Rob Allan wrote:
My biggest gripe is that the Qt Quick object model seems to be much
more poorly supported in C++ than it is in QML. For example, in C++
you
> -Original Message-
> From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: torstaina 22. syyskuuta 2016 4.40
> To: interest@qt-project.org
> Subject: Re: [Interest] Can't build Qt 5.8 alpha (Windows)
>
> On quarta-feira, 21
On quarta-feira, 21 de setembro de 2016 23:23:13 PDT Xavier Bigand wrote:
> I just found a bug report for this build issue :
> https://bugreports.qt.io/browse/QTBUG-55585
>
> Is there already a branch for version 5.8.0 beta?
Not yet.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Softwar
On quarta-feira, 21 de setembro de 2016 20:07:00 PDT Jason H wrote:
> 2. How do I use SecureTransport in Qt? (I googled)
> a. Is this a .pro option?
> b. Is this a recompile Qt thing?
Do not pass -openssl to configure. It will use SecureTransport by default.
--
Thiago Macieira - thiago.macieira
On Wed, Sep 21, 2016 at 05:42:44AM +, Shawn Rutledge wrote:
>
> On Sep 20, 2016, at 22:52, Rob Allan wrote:
> > My biggest gripe is that the Qt Quick object model seems to be much
> > more poorly supported in C++ than it is in QML. For example, in C++
> > you really only have access to QQuick
I just found a bug report for this build issue :
https://bugreports.qt.io/browse/QTBUG-55585
Is there already a branch for version 5.8.0 beta?
2016-09-21 20:51 GMT+02:00 Xavier Bigand :
> With sources from git I had tried to build the branch 5.8.
>
> But as I successfully build the branch 5.7,
Is anyone productivly using Qt 5.6.1 and Xcode 8 on macOS Sierra? Any
show-stoppers problems?
Xcode 8 under OS X 10.11.6 is working for me pretty well.
However I am missing some of the Additional Tools for Xcode 8 because they do
not run on El Capitan.
Thank you for your feedback,
-Ed
Thi
> Am 21.09.2016 um 20:07 schrieb Jason H :
>
>
>>> Does anyone know how I can fix (not hide) these issues?
>>
>> Option 1) upgrade OpenSSL
>>
>> Option 2) use the native backend (SecureTransport) for SSL, not OpenSSL.
>> SecureTransport is the default in Qt 5.6.
>
> Thanks Thiago! But instr
Hi,
Someone may have beaten me to do this:
It seems the latest Xcode GM beta removed the xcrun binary from the Xcode.app
embedded toolchain /usr/bin directory, causing Qt's configure command to fail,
claiming the Xcode license was never accepted.
Attached is a patch that solved the issue for th
> Am 21.09.2016 um 20:01 schrieb Thiago Macieira :
>
>> On quarta-feira, 21 de setembro de 2016 19:52:45 PDT Jason H wrote:
>> I am on OSX 10.11.5. I've been using SSL successfully for a while, and I
>> fell into a habit of ignoring qt.network.ssl warnings: qt.network.ssl:
>> ...
>>
>> But it s
> Sent: Wednesday, September 21, 2016 at 2:07 PM
> From: "Jason H"
> To: "Thiago Macieira"
> Cc: interest@qt-project.org
> Subject: Re: [Interest] SSL broken hard on OSX
>
>
> > > Does anyone know how I can fix (not hide) these issues?
> >
> > Option 1) upgrade OpenSSL
> >
> > Option 2) use
With sources from git I had tried to build the branch 5.8.
But as I successfully build the branch 5.7, I had switch the module qt3d to
branch 5.8 before leaving the office. I mainly want to try some fixes that
I have request on qt3d.
I hope that qt3d 5.8 is compatible with the 5.7.
I also tried t
> > Does anyone know how I can fix (not hide) these issues?
>
> Option 1) upgrade OpenSSL
>
> Option 2) use the native backend (SecureTransport) for SSL, not OpenSSL.
> SecureTransport is the default in Qt 5.6.
Thanks Thiago! But instructions are there instructions? Questions I have:
1. Which
On quarta-feira, 21 de setembro de 2016 19:52:45 PDT Jason H wrote:
> I am on OSX 10.11.5. I've been using SSL successfully for a while, and I
> fell into a habit of ignoring qt.network.ssl warnings: qt.network.ssl:
> QSslSocket: cannot resolve SSL_set_psk_client_callback qt.network.ssl:
> QSslSock
On quarta-feira, 21 de setembro de 2016 12:07:34 PDT Xavier Bigand wrote:
> I try with adding QMAKE_CXXFLAGS+=-Iqtbase\include\QtCore\5.8.0 to the
> configure command, it helps a little, it compile more sources, but I get
> the same error later.
Which Git commit are you compiling now?
--
Thiago
On quarta-feira, 21 de setembro de 2016 09:08:09 PDT André Somers wrote:
> Op 20/09/2016 om 22:09 schreef Alejandro Exojo:
> > On Monday 19 September 2016 18:35:43 Etienne Sandré-Chardonnal wrote:
> >> Yes, but for instance you can't move-pass an object between signals and
> >> slots across a queue
I am on OSX 10.11.5. I've been using SSL successfully for a while, and I fell
into a habit of ignoring qt.network.ssl warnings:
qt.network.ssl: QSslSocket: cannot resolve SSL_set_psk_client_callback
qt.network.ssl: QSslSocket: cannot resolve TLSv1_1_client_method
qt.network.ssl: QSslSocket: cannot
As some recommands to me to build my own version of Qt, I give it a try.
Sadly I am not able to build Qt 5.8 alpha nor the branch 5.8 from git. I
switched to the branch 5.7 that seems to compile correctly (still running).
That exactly why I think that it would be great if binaries of alpha and
bet
This gets at what I don't like about Qt the most: As a user I have no control
of where it goes. I can (and do) file bugs and feature suggestions... How they
get prioritized, I have no control over. Sometimes it's months, sometimes it's
multiple years later, very often it's never (or more correct
21.09.2016, 15:28, "Jean-Michaël Celerier" :
> Hey, there is a lot of interesting points in all these answers; some
> similars, some not.
>
> Maybe a good way forward would be to try to pinpoint the problems more
> precisely with an online platform such
> as http://en.arguman.org/ ? Or even jus
Hey, there is a lot of interesting points in all these answers; some
similars, some not.
Maybe a good way forward would be to try to pinpoint the problems more
precisely with an online platform such
as http://en.arguman.org/ ? Or even just some kind of google doc...
Starting from there would mayb
> I also can't help making a comparison with two other popular layout
> frameworks: WPF/XAML, and Android/AXML. In both of these worlds, the markup
> language and the "code-behind" class hierarchy of UI elements are
> absolutely equivalent 1st class citizens. Anything you can do in XAML, you
> can
I switched from qmake to cmake some five+ years ago and while I don't
regret it, it takes the 'I' out of all the IDEs I use. No class wizard or
real refactoring. Creating a new class or worse library or project takes a
lot of blind text editing. This could only be fixed by a full fledged QBS I
gues
Op 20/09/2016 om 22:09 schreef Alejandro Exojo:
On Monday 19 September 2016 18:35:43 Etienne Sandré-Chardonnal wrote:
Yes, but for instance you can't move-pass an object between signals and
slots across a queued connection, unless I'm wrong. You have to make your
object implicitely shared. Thi
26 matches
Mail list logo