Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Thiago Macieira]

On Wednesday, 20 March 2019 14:59:39 PDT René J.V. Bertin wrote:
> >Because it is a major rewrite of QtNetwork code interfacing with OpenSSL.
> >Such change cannot go to LTS branch [1]
> 
> Now maybe (though I'd argue this is a bug fix; OSSL 1.0 will go EOL 5 months
> before Qt 5.9). But that was not the question.
> 
> 5.9.0 was released on May 31st 2017
> (https://en.wikipedia.org/wiki/Qt_version_history#Qt_5), two full months
> after the fix in question. 

You're looking at the wrong date.
$ git show --pretty=fuller cfbe03a6e035ab3cce5f04962cddd06bd414dcea | head -7
commit cfbe03a6e035ab3cce5f04962cddd06bd414dcea
Author: Richard J. Moore 
AuthorDate: Thu Mar 23 12:43:22 2017 +0100
Commit: André Klitzing 
CommitDate: Tue Jul 4 18:03:59 2017 +

QSslSocket: OpenSSL 1.1 backend

The commit was *begun* two months before the Qt 5.9.0 release, or one month 
after the alpha1 release. It took more than three months from the first upload 
for the change to be accepted. 5.9.1 had been released by that time.

> Qt 5.10 was released half a year later, so the
> fix could easily have gone into 5.9.0 or 5.9.1 .

It was decided not to. As the length of time shows, the development of this 
change was not trivial. Applying it to the released branch was not only a 
violation of the feature freeze, but also potentially irresponsible, since it 
was new code that had bugs. If you search the commit log, you'll see a number 
of OpenSSL 1.1 bugfixes.

PS: you should backport those fixes too.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[René J . V . Bertin]

>Because it is a major rewrite of QtNetwork code interfacing with OpenSSL. Such 
>change
>cannot go to LTS branch [1]

Now maybe (though I'd argue this is a bug fix; OSSL 1.0 will go EOL 5 months 
before Qt 5.9). But that was not the question.

5.9.0 was released on May 31st 2017 
(https://en.wikipedia.org/wiki/Qt_version_history#Qt_5), two full months after 
the fix in question. Qt 5.10 was released half a year later, so the fix could 
easily have gone into 5.9.0 or 5.9.1 .

R.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] How to show always a done button

[Roman Wüger]

Hi Pierre,

I also have no done button if the keyboard is text only. So maybe this function 
doesn‘t work at all on iOS?

Regards
Roman

Am 20.03.2019 um 10:57 schrieb Pierre-Yves Siret :

>> Hi,
>> 
>> I try to always show a done or similar button on top of the onscreen 
>> keyboard.
>> 
>> To do this I tried the following as an example for a Textfield:
>> 
>> inputMethodHints: Qt.ImhDigitsOnly
>> EnterKey.type: Qt.EnterKeyDone
>> 
>> but there is no done key shown.
>> 
>> Any hints?
> 
> I suppose your problem is on iOS?
> Some info I shared in a previous email : 
> https://lists.qt-project.org/pipermail/interest/2018-December/031956.html 
> 
> Regards,
> Pierre-Yves
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Giuseppe D'Angelo via Interest]

Il 20/03/19 19:41, Thiago Macieira ha scritto:

Actually, it doesn't: 5.9 support ends in May 2020, OpenSSL 1.0 in Dec 2019.

You're off by one year. 5.9.0 was released May 29, 2017.

5.9's support ends in May 2019 (probably a bit later because we are able to
make the 5.9.9 release).


Isn't the LTS supported for 3 years? We've now reached EOL for 5.6, 
released in March 2016. Is 5.9 supported only for 2 years?


Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Thiago Macieira]

On Wednesday, 20 March 2019 11:31:39 PDT Giuseppe D'Angelo via Interest wrote:
> > Qt 5.9's lifetime ends before OpenSSL 1.0's.
> 
> Actually, it doesn't: 5.9 support ends in May 2020, OpenSSL 1.0 in Dec 2019.

You're off by one year. 5.9.0 was released May 29, 2017.

5.9's support ends in May 2019 (probably a bit later because we are able to 
make the 5.9.9 release). 

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Giuseppe D'Angelo via Interest]

Il 20/03/19 19:29, Thiago Macieira ha scritto:

Qt 5.9's lifetime ends before OpenSSL 1.0's.


Actually, it doesn't: 5.9 support ends in May 2020, OpenSSL 1.0 in Dec 2019.

The reality is that if your software depends on multiple libraries, your 
deadline is the whichever EOL for those libraries comes first. So, 
again, UPGRADE NOW.


My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Thiago Macieira]

On Wednesday, 20 March 2019 11:14:52 PDT René J. V. Bertin wrote:
> See my other email: for now this is for MacPorts, but I'm guessing Qt may
> not want to depend only on an OpenSSL variant that's EOL.

Except that it's not EOL. OpenSSL 1.0.2 is still officially supported until 
2019-12-31. See https://www.openssl.org/policies/releasestrat.html

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Konstantin Tokarev]

20.03.2019, 21:17, "René J. V. Bertin" :
>>  Which distribution already stopped shipping OpenSSL 1.0?
>
> See my other email: for now this is for MacPorts, but I'm guessing Qt may not
> want to depend only on an OpenSSL variant that's EOL.
>
> Moving to 5.10 may be relatively trivial on Linux but not on Mac, if you want 
> to
> keep supporting OS versions that don't run 5.10 .
>
> Judging from the commit, OSSL 1.1 support was added to the dev branch almost
> exactly TWO years ago. I can't remember when 5.9 came out but it must not have
> been older than the "current" version back then. Why on earth was this change
> never cherry-picked to the 5.9 branch?!

Because it is a major rewrite of QtNetwork code interfacing with OpenSSL. Such 
change
cannot go to LTS branch [1]

[1] http://quips-qt-io.herokuapp.com/quip-0005.html

> It's not like it introduces all kinds of
> hot new features, and if I understand correctly this kind of change to the 
> OSSL
> backend should be completely transparent for dependent software?
>
> R.
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest

-- 
Regards,
Konstantin

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Thiago Macieira]

On Wednesday, 20 March 2019 03:15:38 PDT René J.V. Bertin wrote:
> Hi,
> 
> I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 .
> Does anyone already have a fix for this?

Forklift the support from 5.10. A couple of Linux distributions did that for a 
while (notably, OpenSUSE).

> If not I'll try to adapt Debian's OSSL 1.1 support patch for Qt4; that might
> even be upstreamable supposing there will be further Qt 5.9 releases ?

5.9.8 is coming and 5.9.9 is likely. But there will be no OpenSSL 1.1 support 
patch accepted to those.

Qt 5.9's lifetime ends before OpenSSL 1.0's.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Unable to build Qt 5.12 on Ubuntu 14.04

[Thiago Macieira]

On Wednesday, 20 March 2019 06:29:19 PDT Kevin Funk wrote:
> Also, another hint for you and the other person(s) trying to build recent Qt
> on an old Ubuntu LTS: Note that Ubuntu 14.04 is reaching end-of-life in one
> month(!), and only the ESM version contains further security fixes.
> 
> See:
>   https://blog.ubuntu.com/2019/02/05/ubuntu-14-04-trusty-tahr
> 
> Time to upgrade I think. You're two LTS versions behind.

Which is one of the reasons that dropping the bundled xkbcommon was 
acceptable: recent enough distros have it.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[René J . V . Bertin]

Konstantin Tokarev wrote:

> It would be better to upgrade Qt in MacPorts

MacPorts provides the latest and also a whole range of older Qt versions (down 
to Qt 5.5 I think). It has to, because Qt doesn't support a sufficient range of 
OS versions for our purposes.

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[René J . V . Bertin]

> Which distribution already stopped shipping OpenSSL 1.0?

See my other email: for now this is for MacPorts, but I'm guessing Qt may not 
want to depend only on an OpenSSL variant that's EOL.

Moving to 5.10 may be relatively trivial on Linux but not on Mac, if you want 
to 
keep supporting OS versions that don't run 5.10 .

Judging from the commit, OSSL 1.1 support was added to the dev branch almost 
exactly TWO years ago. I can't remember when 5.9 came out but it must not have 
been older than the "current" version back then. Why on earth was this change 
never cherry-picked to the 5.9 branch?! It's not like it introduces all kinds 
of 
hot new features, and if I understand correctly this kind of change to the OSSL 
backend should be completely transparent for dependent software?

R.

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Konstantin Tokarev]

20.03.2019, 21:03, "René J.V. Bertin" :
>> You should either use Qt >= 5.10 or build against OpenSSL 1.0.2
>
> Wrong answer :P
>
> If Qt 5.9 is still in LTS it should get commit 
> cfbe03a6e035ab3cce5f04962cddd06bd414dcea cherry picked from the dev branch 
> before 1.0 reaches EOL later this year.
>
> Is that commit sufficient? Getting it to apply to the 5.9 branch was a bit of 
> monks' work but perfectly doable;
> see https://trac.macports.org/ticket/58218
>
> The MacPorts project is in the process of migrating the default OpenSSL 
> version to 1.1 . I haven't yet upgraded but am preparing; my patched Qt 5.9.7 
> seems to work fine with OSSL 1.0.2r .

It would be better to upgrade Qt in MacPorts

>
> David: IIRC Qt doesn't work with LibreSSL.
>
> R.

-- 
Regards,
Konstantin

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[René J . V . Bertin]

>You should either use Qt >= 5.10 or build against OpenSSL 1.0.2

Wrong answer :P

If Qt 5.9 is still in LTS it should get commit 
cfbe03a6e035ab3cce5f04962cddd06bd414dcea cherry picked from the dev branch 
before 1.0 reaches EOL later this year.

Is that commit sufficient? Getting it to apply to the 5.9 branch was a bit of 
monks' work but perfectly doable;
see https://trac.macports.org/ticket/58218

The MacPorts project is in the process of migrating the default OpenSSL version 
to 1.1 . I haven't yet upgraded but am preparing; my patched Qt 5.9.7 seems to 
work fine with OSSL 1.0.2r .

David: IIRC Qt doesn't work with LibreSSL.

R.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Giuseppe D'Angelo via Interest]

Hi,

Il 20/03/19 18:23, David M. Cotter ha scritto:

I understand LibreSSL has some advantages, is that worth checking out?


Qt does not work with LibreSSL.

Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Giuseppe D'Angelo via Interest]

Il 20/03/19 11:15, René J.V. Bertin ha scritto:

I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 . Does 
anyone already have a fix for this?


Which distribution already stopped shipping OpenSSL 1.0?

Cheers,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[Konstantin Tokarev]

20.03.2019, 13:18, "René J.V. Bertin" :
> Hi,
>
> I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 . 
> Does anyone already have a fix for this?

You should either use Qt >= 5.10 or build against OpenSSL 1.0.2

>
> If not I'll try to adapt Debian's OSSL 1.1 support patch for Qt4; that might 
> even be upstreamable supposing there will be further Qt 5.9 releases ?
>
> Thanks,
> R.
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest

-- 
Regards,
Konstantin

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.9 and OpenSSL 1.1?

[David M. Cotter]

I understand LibreSSL has some advantages, is that worth checking out?

> On Mar 20, 2019, at 3:15 AM, René J.V. Bertin  wrote:
> 
> Hi,
> 
> I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 . 
> Does anyone already have a fix for this?
> 
> If not I'll try to adapt Debian's OSSL 1.1 support patch for Qt4; that might 
> even be upstreamable supposing there will be further Qt 5.9 releases ?
> 
> Thanks,
> R.
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Unable to build Qt 5.12 on Ubuntu 14.04

[Kevin Funk]

On Wednesday, 20 March 2019 13:01:18 CET Sérgio Martins via Interest wrote:
> On 2019-03-20 11:24, Calogero Mauceri wrote:
> > On Tue, Mar 19, 2019 at 7:54 PM Thiago Macieira
> > 
> > 
> > wrote:
> >> On Tuesday, 19 March 2019 09:40:42 PDT Calogero Mauceri wrote:
> >> > Hi all,
> >> > 
> >> > I'm trying to build Qt 5.12.2 on Ubuntu 14.04.
> >> > I get the following error just after I launch the configure
> >> > 
> >> > ERROR: Feature 'xcb' was enabled, but the pre-condition
> >> > 'features.thread
> >> 
> >> &&
> >> 
> >> > features.xkbcommon && libs.xcb' failed.
> >> > 
> >> > here is the configure line I'm using
> >> > 
> >> > ./configure -qt-zlib -fontconfig -qt-xcb
> >> > 
> >> > I have libxcb1 and libxcb1-dev 1.10-2ubuntu1 installed on the system.
> >> > I am building on a 32 bit system, but I get the same error on a 64 bit
> >> > machine.
> >> > Am I missing some other dependencies? Do you know how to check?
> >> 
> >> Yes, the error message told you which one: "features.xkbcommon &&
> >> libs.xcb".
> >> Since you have installed the XCB libraries, you should check for
> >> xkbcommon
> >> ones.
> >> 
> >> If you have libxcb1-dev installed, why are you passing -qt-xcb? And,
> >> for
> >> that
> >> matter, why -qt-zlib? Just use your distro's packages for those.
> > 
> > Thanks Thiago for your reply,
> > 
> > xkbcommon is installed on the machine, version 0.4.1, but we still get
> > that
> > issue.
> > We are building qt with the -qt-xcb option to limit the number of
> > system
> > dependencies for our application.
> 
> You need version 0.5.0 at least.
> 
>  From the ChangeLog [1]:
> "
> [QTBUG-65503] Removed xkbcommon from bundled sources. This library is
> present on all supported platforms. The minimal required version now
> is
> 0.5.0.
> "

Heya,

Also, another hint for you and the other person(s) trying to build recent Qt 
on an old Ubuntu LTS: Note that Ubuntu 14.04 is reaching end-of-life in one 
month(!), and only the ESM version contains further security fixes.

See:
  https://blog.ubuntu.com/2019/02/05/ubuntu-14-04-trusty-tahr

Time to upgrade I think. You're two LTS versions behind.

Regards,
Kevin


> [1] -
> https://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.12.1


-- 
Kevin Funk | kf...@kde.org | http://kfunk.org

signature.asc
Description: This is a digitally signed message part.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Unable to build Qt 5.12 on Ubuntu 14.04

[Sérgio Martins via Interest]

On 2019-03-20 11:24, Calogero Mauceri wrote:
On Tue, Mar 19, 2019 at 7:54 PM Thiago Macieira 


wrote:


On Tuesday, 19 March 2019 09:40:42 PDT Calogero Mauceri wrote:
> Hi all,
>
> I'm trying to build Qt 5.12.2 on Ubuntu 14.04.
> I get the following error just after I launch the configure
>
> ERROR: Feature 'xcb' was enabled, but the pre-condition 'features.thread
&&
> features.xkbcommon && libs.xcb' failed.
>
> here is the configure line I'm using
>
> ./configure -qt-zlib -fontconfig -qt-xcb
>
> I have libxcb1 and libxcb1-dev 1.10-2ubuntu1 installed on the system.
> I am building on a 32 bit system, but I get the same error on a 64 bit
> machine.
> Am I missing some other dependencies? Do you know how to check?

Yes, the error message told you which one: "features.xkbcommon &&
libs.xcb".
Since you have installed the XCB libraries, you should check for 
xkbcommon

ones.

If you have libxcb1-dev installed, why are you passing -qt-xcb? And, 
for

that
matter, why -qt-zlib? Just use your distro's packages for those.



Thanks Thiago for your reply,

xkbcommon is installed on the machine, version 0.4.1, but we still get 
that

issue.
We are building qt with the -qt-xcb option to limit the number of 
system

dependencies for our application.


You need version 0.5.0 at least.

From the ChangeLog [1]:
"
[QTBUG-65503] Removed xkbcommon from bundled sources. This library is
   present on all supported platforms. The minimal required version now 
is

   0.5.0.
"

[1] - 
https://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.12.1/?h=v5.12.1

--
Sérgio Martins | sergio.mart...@kdab.com | Senior Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - The Qt, C++ and OpenGL Experts
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Problems getting QGeoPositionInfoSource working under iOS

[Alex Blasche]

Hi,

Here are a few hints what you might want to check upon.

Do you use cmake or qmake? cmake does not work with static libs. You must use 
qmake as it works out what dependencies have to be build into binary.

I suggest you go through your binaries and first verify that you have the 
relevant qtposition plugin in your set of binaries. It would be under
Qt/5.12.0/ios/plugins/position/libqtposition_cl.a. As second step ensure that 
this plugin is part of your applications link line. Last but not least ensure 
that your application's project file specifically mentions positioning as 
dependency.

--
Alex


From: Roman Wüger 
Sent: Wednesday, 20 March 2019 10:07:52 AM
To: Alex Blasche
Cc: Qt Project MailingList
Subject: Re: [Interest] Problems getting QGeoPositionInfoSource working under 
iOS

Hello Alex,

I use the prebuilt binaries from the online Installer.

Regards
Roman

> Am 20.03.2019 um 08:51 schrieb Alex Blasche :
>
> Hi,
>
>> From: Interest  on behalf of Roman Wüger 
>> 
>
>> I try to get QGeoPositionInfoSource::createDefaultSource(this); working 
>> under iOS 12.1.2 with Qt 5.11.x.
>> But the function returns always a null pointer.
>
> In general this should work out of the box unless there is a bug...
>
> How did you obtain the binaries? Did you build them by yourself or did you 
> use binaries obtained via the installer. If you build by yourself please 
> ensure that
>
> https://code.qt.io/cgit/qt/qtlocation.git/tree/src/plugins/position/corelocation
>
> is built into your binaries.
>
> --
> Alex
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Unable to build Qt 5.12 on Ubuntu 14.04

[Calogero Mauceri]

On Tue, Mar 19, 2019 at 7:54 PM Thiago Macieira 
wrote:

> On Tuesday, 19 March 2019 09:40:42 PDT Calogero Mauceri wrote:
> > Hi all,
> >
> > I'm trying to build Qt 5.12.2 on Ubuntu 14.04.
> > I get the following error just after I launch the configure
> >
> > ERROR: Feature 'xcb' was enabled, but the pre-condition 'features.thread
> &&
> > features.xkbcommon && libs.xcb' failed.
> >
> > here is the configure line I'm using
> >
> > ./configure -qt-zlib -fontconfig -qt-xcb
> >
> > I have libxcb1 and libxcb1-dev 1.10-2ubuntu1 installed on the system.
> > I am building on a 32 bit system, but I get the same error on a 64 bit
> > machine.
> > Am I missing some other dependencies? Do you know how to check?
>
> Yes, the error message told you which one: "features.xkbcommon &&
> libs.xcb".
> Since you have installed the XCB libraries, you should check for xkbcommon
> ones.
>
> If you have libxcb1-dev installed, why are you passing -qt-xcb? And, for
> that
> matter, why -qt-zlib? Just use your distro's packages for those.
>

Thanks Thiago for your reply,

xkbcommon is installed on the machine, version 0.4.1, but we still get that
issue.
We are building qt with the -qt-xcb option to limit the number of system
dependencies for our application.

-- 
Calogero Mauceri
Software Engineer

Applied Coherent Technology Corporation (ACT)
www.actgate.com
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] a question about QNetworkAccessManager

[Mårten Nordheim]

One QNetworkAccessManager (QNAM for short) will be enough in your case as well. 
The signals on QNAM all pass a pointer to the QNetworkReply so you can know 
which it relates to.
Although perhaps more fitting for your usecase may be to use the signals on 
QNetworkReply instead of QNAM 
https://doc.qt.io/qt-5/qnetworkreply.html#finished?

Regards,
Mårten

From: Matej Košík
Sent: onsdag 20. mars 2019 10:47
To: interest@qt-project.org
Subject: [Interest] a question about QNetworkAccessManager

Hi,

I am new to Qt.
Yesterday, I have learned about:
- QNetworkAccessManager
- QNetworkRequest
- QNetworkReply
(as I wanted to figure out how to make HTTP GET/POST request and process the 
responses).

Here:

  https://doc.qt.io/qt-5/qnetworkaccessmanager.html#details

I read:

  One QNetworkAccessManager instance should be enough for the whole Qt 
application.

I do not understand what do I gain by that.
Our application makes different HTTP requests.
Each response must be handled differently.
Why would we want to pipe all "finished" signals (generated by the 
QNetworkAccessManager) to the same set of slots?
What sense would that make?

---

Curiously,
Matej

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Qt 5.9 and OpenSSL 1.1?

[René J . V . Bertin]

Hi,

I just learned that Qt 5.9 apparently doesn't build against OpenSSL 1.1 . Does 
anyone already have a fix for this?

If not I'll try to adapt Debian's OSSL 1.1 support patch for Qt4; that might 
even be upstreamable supposing there will be further Qt 5.9 releases ?

Thanks,
R.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] a question about QNetworkAccessManager

[Reinhardt Behm via Interest]

On Wednesday 20 March 2019 10:45:18 you wrote:
> Hi,
> 
> I am new to Qt.
> Yesterday, I have learned about:
> - QNetworkAccessManager
> - QNetworkRequest
> - QNetworkReply
> (as I wanted to figure out how to make HTTP GET/POST request and process the
> responses).
> 
> Here:
> 
>   https://doc.qt.io/qt-5/qnetworkaccessmanager.html#details
> 
> I read:
> 
>   One QNetworkAccessManager instance should be enough for the whole Qt
> application.
> 
> I do not understand what do I gain by that.
> Our application makes different HTTP requests.
> Each response must be handled differently.
> Why would we want to pipe all "finished" signals (generated by the
> QNetworkAccessManager) to the same set of slots? What sense would that
> make?
> 
> ---
> 
> Curiously,
> Matej

Then simply don't do this. Connect the finished signal from the generated 
QNetworkReply to the corresponding slot.

In this slot you should also delete the QNR (with deleteLater() ) because 
otherwise it will exist forever and eat up memory.

-- 
Best Regards

Reinhardt Behm


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] How to show always a done button

[Pierre-Yves Siret]

>
> Hi,
>
> I try to always show a done or similar button on top of the onscreen
> keyboard.
>
> To do this I tried the following as an example for a Textfield:
>
> inputMethodHints: Qt.ImhDigitsOnly
> EnterKey.type: Qt.EnterKeyDone
>
> but there is no done key shown.
>
> Any hints?
>

I suppose your problem is on iOS?
Some info I shared in a previous email :
https://lists.qt-project.org/pipermail/interest/2018-December/031956.html

Regards,
Pierre-Yves
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] [SPAM] a question about QNetworkAccessManager

[Matej Košík]

Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Hi, I am new to Qt. Yesterday, I have learned about: - 
QNetworkAccessManager
   - QNetworkRequest - QNetworkReply (as I wanted to figure out how to make
  HTTP GET/POST request and process the responses). [...] 

Content analysis details:   (4.7 points, 4.0 required)

 pts rule name  description
 -- --
 0.0 URIBL_BLOCKED  ADMINISTRATOR NOTICE: The query to URIBL was 
blocked.
See

http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
 for more information.
[URIs: qt.io]
 0.8 BAYES_50   BODY: Bayes spam probability is 40 to 60%
[score: 0.5000]
 0.7 SPF_HELO_SOFTFAIL  SPF: HELO does not match SPF record (softfail)
 1.0 FROM_EXCESS_BASE64 From: base64 encoded unnecessarily
 1.2 KHOP_DYNAMIC   Relay looks like a dynamic address
 1.0 RDNS_DYNAMIC   Delivered to internal network by host with
dynamic-looking rDNS


--- Begin Message ---
Hi,

I am new to Qt.
Yesterday, I have learned about:
- QNetworkAccessManager
- QNetworkRequest
- QNetworkReply
(as I wanted to figure out how to make HTTP GET/POST request and process the 
responses).

Here:

  https://doc.qt.io/qt-5/qnetworkaccessmanager.html#details

I read:

  One QNetworkAccessManager instance should be enough for the whole Qt 
application.

I do not understand what do I gain by that.
Our application makes different HTTP requests.
Each response must be handled differently.
Why would we want to pipe all "finished" signals (generated by the 
QNetworkAccessManager) to the same set of slots?
What sense would that make?

---

Curiously,
Matej
--- End Message ---
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Problems getting QGeoPositionInfoSource working under iOS

[Roman Wüger]

Hello Alex,

I use the prebuilt binaries from the online Installer.

Regards
Roman

> Am 20.03.2019 um 08:51 schrieb Alex Blasche :
> 
> Hi,
> 
>> From: Interest  on behalf of Roman Wüger 
>> 
> 
>> I try to get QGeoPositionInfoSource::createDefaultSource(this); working 
>> under iOS 12.1.2 with Qt 5.11.x.
>> But the function returns always a null pointer.
> 
> In general this should work out of the box unless there is a bug...
> 
> How did you obtain the binaries? Did you build them by yourself or did you 
> use binaries obtained via the installer. If you build by yourself please 
> ensure that 
> 
> https://code.qt.io/cgit/qt/qtlocation.git/tree/src/plugins/position/corelocation
> 
> is built into your binaries. 
> 
> --
> Alex
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Problems getting QGeoPositionInfoSource working under iOS

[Alex Blasche]

Hi,

>From: Interest  on behalf of Roman Wüger 
>

>I try to get QGeoPositionInfoSource::createDefaultSource(this); working under 
>iOS 12.1.2 with Qt 5.11.x.
>But the function returns always a null pointer.

In general this should work out of the box unless there is a bug...

How did you obtain the binaries? Did you build them by yourself or did you use 
binaries obtained via the installer. If you build by yourself please ensure 
that 

https://code.qt.io/cgit/qt/qtlocation.git/tree/src/plugins/position/corelocation

is built into your binaries. 

--
Alex
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QTest

[Thiago Macieira]

On Tuesday, 19 March 2019 16:46:49 PDT Jérôme Godbout wrote:
> I run qTest::exec() to run my test but I would like to known if it's
> possible to recover the number of failure/pass/skipped to do some work
> after the qTest::exec()

That information is logged, but is not exposed in the API.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products



___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Problems getting QGeoPositionInfoSource working under iOS

[Roman Wüger]

Hi,

I try to get QGeoPositionInfoSource::createDefaultSource(this); working under 
iOS 12.1.2 with Qt 5.11.x.
But the function returns always a null pointer. 

Do i need to initialize the plugin first?
Maybe with Q_IMPORT_PLUGIN?
But if so, what do I need to enter?

Thanks in advance

Regards
Roman
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] How to show always a done button

[Roman Wüger]

Hi,

I try to always show a done or similar button on top of the onscreen keyboard.

To do this I tried the following as an example for a Textfield:

inputMethodHints: Qt.ImhDigitsOnly
EnterKey.type: Qt.EnterKeyDone

but there is no done key shown.

Any hints?

Regards
Roman
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] QWizard - can't register a field with a custom property

[Frank Rueter | OHUfx]

I now have the same issue with trying to register a QTextEdit widget's 
content:


|self.registerField('message', self.notes_widget.messageWidget, 
'toPlainText', 'notes_widget.messageWidget.textChanged') |


Once again my sanity check with manual signal/slot connections works fine:

|self.notes_widget.messageWidget.textChanged.connect(self.test) def 
test(self): print self.notes_widget.messageWidget.toPlainText() |


What am I missing?

Cheers,
frank

On 20/03/19 10:08 AM, Frank Rueter | OHUfx wrote:


Hi all,

In a QWizard page I am trying to register a field with a widget’s 
custom property to supply the desired field value but I can’t get it 
to work.
This is the line I am using to register the field and to link it to 
the signal that informs the field to update it’s value:


|self.registerField('to_list', self.notes_widget.to_list_widget, 
'get_all_data', 'notes_widget.to_list_widget.current_data_changed') |


When I query the field later via self.field(;to_list’) I just get None.

As a sanity check I hooked up the signal to a test slot like this:

|self.notes_widget.to_list_widget.current_data_changed.connect(self.test) 
test(self): print 'to test:', 
self.notes_widget.to_list_widget.get_all_data() |


The latter works just fine.
Can anybody spot what I’m doing wrong?

Cheers,
frank

​
--

ohufxLogo 50x50 
	*vfx compositing  | *workflow 
customisation and consulting * *

**
   


Your gateway to over 1,000 free tools... right inside of Nuke 




___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest


​
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest