Re: [Interest] Porting Qt to our RTOS

Good reference. Thanks! -Original Message- From: Interest On Behalf Of Thiago Macieira Sent: Thursday, September 27, 2018 12:15 PM To: interest@qt-project.org Subject: Re: [Interest] Porting Qt to our RTOS On Wednesday, 26 September 2018 23:53:17 PDT Tuukka Turunen wrote: > Hi Kim, >

Re: [Interest] Porting Qt to our RTOS

Thanks Tuuka (and others), We've ported much of the BOOST libraries, so pthreads are most possible. I've started an internal audit of the rest of POSIX services we would need in order to create an INtime QPA. Is there a more comprehensive list of POSIX calls needed for GUI functionality? Is

Re: [Interest] Porting Qt to our RTOS

On Thursday, 27 September 2018 09:03:55 PDT Giuseppe D'Angelo via Interest wrote: > Il 27/09/2018 17:14, Roland Hughes ha scritto: > > On 9/27/18 1:53 AM, Kim Hartman wrote: > > The short answer is that you shouldn't. > > > > The AGILE processes behind Qt development > > 1) This is an unproven

Re: [Interest] Porting Qt to our RTOS

On Wednesday, 26 September 2018 23:53:17 PDT Tuukka Turunen wrote: > Hi Kim, > > Even partial Posix will help you get going. It is possible to do without, > but then more work will be needed. I echo the part about POSIX. If you don't have a POSIX layer, you're going to have to port even things

Re: [Interest] Porting Qt to our RTOS

Il 27/09/2018 17:14, Roland Hughes ha scritto: On 9/27/18 1:53 AM, Kim Hartman  wrote: I am investigating how to bring Qt to our INtime RTOS. The INtime Distributed RTOS runs on standard PC hardware as a multicore AMP OS (no SMP and not POSIX compliant). Currently the RTOS has only a text

Re: [Interest] Porting Qt to our RTOS

On 9/27/18 1:53 AM, Kim Hartman  wrote: I am investigating how to bring Qt to our INtime RTOS. The INtime Distributed RTOS runs on standard PC hardware as a multicore AMP OS (no SMP and not POSIX compliant). Currently the RTOS has only a text console output based on INT10 services. The RTOS

Re: [Interest] QML Settings fails persistance on Android

For now I've reported QTBUG-70419 , with my own suggestion for the fix. It's been given P1. /René On Fri, 31 Aug 2018 at 18:09 Paolo Angelelli wrote: > I also have had several issues (mostly persistence issues) with > Qt.labs.settings. > In the end

Re: [Interest] Vote for Windows 32-Bit Binaries for MSVC-2017

You should be more precise, as in "If somebody wants to build Qt WebEngine for 32-bit MSVC2017"... All other modules build fine, it's my day to day setup. Maurice -Original Message- From: Interest On Behalf Of coroberti . Sent: Thursday, September 27, 2018 9:00 AM To: Qt Interest

[Interest] Vote for Windows 32-Bit Binaries for MSVC-2017

Hi, Please, consider voting for: https://bugreports.qt.io/browse/QTBUG-63708 Note, that if somebody wants to build Qt for 32-bit MSVC-2017 by himself/herself, cross compiler to be used since Qt-5.11 and up in line with the tips in: https://bugreports.qt.io/browse/QTBUG-68462 Note, that since

Re: [Interest] Porting Qt to our RTOS

Hi Kim, Even partial Posix will help you get going. It is possible to do without, but then more work will be needed. When looking into QPA, perhaps the one for INTEGRITY is the one that you want to start with. What kind of hardware and applications you are thinking about? Yours,