Coressent Korea - Freescale i.MX6 RTEMS/Qt SDK Release Information.
JunBeom Kim (Coressent)
jbkim at coressentkorea.co.kr
Tue Jul 14 06:24:55 UTC 2015
Thank you very much for your comment.
- I will try to use rtems-libbsd soon regarding this.
- Qt 4.8 can be built without mmap feature.
- If I need mmap for Qt 5.x, I will use your mmap code. Thank you.
- I tried to implemented fstatvfs() for Qt. but, I was failed.
- As I check from GCC toolchain for Linux, there is fstatvfs(). But, there
is not this function from GCC toolchain for RTEMS. I don't know reason. If
there is a method for adding this function on RSB build process, this
problem will be resolved.
4. Shared library
- I didn't test libdl for this. I will try to use libdl for porting WebKit
of Qt 4.8 or WebEngine of Qt 5.5.
5. Your comment, "How do they build Qt with the same code base ?"
- I referenced QNX interface layer due to almost same POSIX API. But, API
between QNX and RTEMS is not equal in 100%. Therefore, a user should patch
From: Chris Johns [mailto:chrisj at rtems.org]
Sent: Tuesday, July 14, 2015 3:00 PM
To: JunBeom Kim (Coressent); 'Gedare Bloom'
Cc: users at rtems.org
Subject: Re: Coressent Korea - Freescale i.MX6 RTEMS/Qt SDK Release
On 14/07/2015 2:56 pm, JunBeom Kim (Coressent) wrote:
> - select() : select() function should be patched for calling select() by
Qt Event dispatcher.
The rtems-libbsd project may help here.
> - mmap() : because mmap is not supported on RTEMS, Qt should be patched.
Do these files ....
> - fstatvfs() : because fstatvfs() is not supported in GCC toolchain
library, Qt File Dialog should be disabled.
Could you add this support to RTEMS ?
> - shared library : because this is not supported, QtWebKit can not be
There is libdl. What is the API used ?
> - OpenGL ES : because there is not OpenGL ES for RTEMS, Qt Quick can not
be ported. If there is OpenGL ES driver for RTEMS, there is possibility for
porting Qt Quick.
> - No process model : because RTEMS can not support OS process model, Qt
pthread only is supported.
Correct, RTEMS is a single address space.
> 2. Qt License issue.
> I have discussed with Qt company regarding Qt distribution for RTEMS in
> Important thing is that Qt source should be modified in many parts due to
RTEMS technical issue.
> Because we modified Qt source and Qt library is linked with RTEMS
statically, we can not provide open community or customers with Qt porting
source code(Open Source License / GPL&LGPL). That is, customer should
purchase Qt commercial license. This is very headache issue in customer
> If user want to use RTOS solution on Qt open source license, there are
three RTOS solution vendors(QNX, VxWorks, Integrity). But, these RTOS
solution have royalty business model.
> I guess that Qt license is better condition than RTOS license.
How do they build Qt with the same code base ?
More information about the users