Coressent Korea - Freescale i.MX6 RTEMS/Qt SDK Release Information.

[Chris Johns]

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 ....

 https://git.rtems.org/chrisj/rtl.git/tree/mmap.c
 https://git.rtems.org/chrisj/rtl.git/tree/munmap.c
 https://git.rtems.org/chrisj/rtl.git/tree/mmap-internal.h

help ?

> - 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 ported.

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 many times.
> 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 considering point.
> 
> 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 ?

Chris