Re: [Interest] Wayland QPA in Qt 5.12.8 LTS

[Ramakanth Kesireddy]

Planning to use Weston.
Do I need to pass -qpa Wayland and build the Qtwayland module?

Best Regards,
Ramakanth

On Fri, 15 May, 2020, 00:45 Thiago Macieira, 
wrote:

> On Thursday, 14 May 2020 09:31:35 PDT Ramakanth Kesireddy wrote:
> > LinuxFB as QPA backend works well with our applications.
> >
> > However, there are other processes which use Qt now so that would like to
> > extend the usecases with Wayland by setting Wayland as QPA if it would
> > support with TI sdk provided since there could be one QApplication
> > instance.
>
> What compositor do you plan to use?
>
> --
> 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 mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Fail to compile qt4 on Ubuntu 20.04.

[Thiago Macieira]

On domingo, 17 de maio de 2020 16:32:19 PDT Hongyi Zhao wrote:
> ../../include/QtCore/../../src/corelib/tools/qpair.h:62:20: note:
> because ‘QPair’ has user-provided ‘QPair& QPair T2>::operator=(const QPair&) [with T1 = int; T2 = int]’
>62 | QPair =(const QPair )

You didn't paste the error message. The error message says "error:".

Please paste the first error line.

-- 
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] Fail to compile qt4 on Ubuntu 20.04.

[Giuseppe D'Angelo via Interest]

Il 18/05/20 01:32, Hongyi Zhao ha scritto:

# The following step failed for Ubuntu 20.04:
$ make -j4
../../include/QtCore/../../src/corelib/tools/qpair.h:62:20: note:
because ‘QPair’ has user-provided ‘QPair& QPair::operator=(const QPair&) [with T1 = int; T2 = int]’
62 | QPair =(const QPair )
   |^~~~
make[1]: *** [Makefile:18175: .obj/release-shared/qsslsocket_openssl.o] Error 1
make[1]: Leaving directory
'/home/werner/Downloads/qt-everywhere-opensource-src-4.8.7/src/network'
make: *** [Makefile:278: sub-network-make_default-ordered] Error 2



This is missing the actual error messages, please run make -j1 and paste 
everything. From the text, it looks like a deprecation warning for a 
custom declared operator=, but that should be just a warning and not an 
error. If some -Werror is in place, find the way to remove it.


The actual error seems to be related to OpenSSL, which you should just 
disable via the respective configure switch (Qt 4 does not support 
OpenSSL 1.1).


HTH,
--
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

[Interest] Fail to compile qt4 on Ubuntu 20.04.

[Hongyi Zhao]

Hi,

Ubuntu 20.04 dropped the qt4 from its official repo, but sometimes I
still want to use it.  So I try to compile it from the source but
failed.  See the info below:

$ wget 
https://download.qt.io/archive/qt/4.8/4.8.7/qt-everywhere-opensource-src-4.8.7.tar.gz
$ tar -zxvf qt-everywhere-opensource-src-4.8.7.tar.gz
$ cd qt-everywhere-opensource-src-4.8.7
$ ./configure

# The following step failed for Ubuntu 20.04:
$ make -j4
../../include/QtCore/../../src/corelib/tools/qpair.h:62:20: note:
because ‘QPair’ has user-provided ‘QPair& QPair::operator=(const QPair&) [with T1 = int; T2 = int]’
   62 | QPair =(const QPair )
  |^~~~
make[1]: *** [Makefile:18175: .obj/release-shared/qsslsocket_openssl.o] Error 1
make[1]: Leaving directory
'/home/werner/Downloads/qt-everywhere-opensource-src-4.8.7/src/network'
make: *** [Makefile:278: sub-network-make_default-ordered] Error 2

Any hints for this problem?

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

Re: [Interest] is it ok to push audio on a background thread, not a timer?

[Thiago Macieira]

On domingo, 17 de maio de 2020 16:10:08 PDT David M. Cotter wrote:
> i have a cross platform (mac / win) app that plays audio.
> i'm using the push method for audio PCM
> instead of using a timer, i'm just running the pump on a background thread.
> 
> This works fine on mac, but produces silence on windows.
> 
> is this... a limitation?

No, it's a bug in your code.

Like every QObject class, unless noted otherwise, you may not call methods on 
the object from outside the object's thread of affinity (the one it was 
created in or moved to with moveToThread). Your code is abusing the API in 
both cases if you're using the API from another thread.

-- 
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] is it ok to push audio on a background thread, not a timer?

[David M. Cotter]

i have a cross platform (mac / win) app that plays audio.
i'm using the push method for audio PCM
instead of using a timer, i'm just running the pump on a background thread.

This works fine on mac, but produces silence on windows.

is this... a limitation?

more info here:
https://forum.qt.io/topic/114921/pumping-audio-on-a-background-thread-not-a-timer
 


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