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 there such a thing as a generic QPA?
Kim
-----Original Message-----
From: Tuukka Turunen <tuukka.turu...@qt.io>
Sent: Wednesday, September 26, 2018 11:53 PM
To: Jason H <jh...@gmx.com>; Kim Hartman <kim.hart...@tenasys.com>
Cc: interest@qt-project.org
Subject: 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,
Tuukka
On 27/09/2018, 6.34, "Interest on behalf of Jason H"
<interest-bounces+tuukka.turunen=qt...@qt-project.org on behalf of
jh...@gmx.com> wrote:
I think POSIX will make it very l vastly easier. But a graphical raster
framebuffer should be doable. Look at QPA, the platform plugin architecture and
see what you can adapt.
Warning: I've never tried to do it.
> Sent: Thursday, September 27, 2018 at 2:09 AM
> From: "Kim Hartman" <kim.hart...@tenasys.com>
> To: "interest@qt-project.org" <interest@qt-project.org>
> Subject: [Interest] Porting Qt to our RTOS
>
> 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 is fully preemptive, with strict priority based
scheduling, managed process services with rich IPC services. The development
environment is tightly coupled with MS VC (2008 and on) with ANSI C and C++11
language support. The RTOS is very stable and been commercially deployed for
decades. It lacks a means for graphical programming, mostly for industrial
controls application. What is the means to port Qt to this RTOS? We're not
intending on building out OpenGL ES 2.0 unless absolutely necessary. I've read
some marketing materials about Qt on MCU, however the details seem very thin.
It's not Windows, Linux, OSX, Android, QNX, Integrity, or VxWorks... how to go
about getting this done?
> _______________________________________________
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
