Raspberry Pi Rtems-Graphical-Toolkit
Kirspel, Kevin
Kevin-Kirspel at idexx.com
Tue May 1 17:01:06 UTC 2018
Another option is to not use X11 and draw directly to the frame buffer device (i.e. /dev/fb0). Qt supports this.
Kevin Kirspel
Electrical Engineer - Sr. Staff
Idexx Roswell
235 Hembree Park Drive
Roswell GA 30076
Tel: (770)-510-4444 ext. 81642
Direct: (770)-688-1642
Fax: (770)-510-4445
From: users [mailto:users-bounces at rtems.org] On Behalf Of Emre Cetin
Sent: Tuesday, May 01, 2018 12:15 PM
To: users at rtems.org
Subject: Fwd: Raspberry Pi Rtems-Graphical-Toolkit
---------- Forwarded message ----------
From: Emre Cetin <hsnemrecetin at gmail.com<mailto:hsnemrecetin at gmail.com>>
Date: 2018-05-01 19:13 GMT+03:00
Subject: Re: Raspberry Pi Rtems-Graphical-Toolkit
To: Chris Johns <chrisj at rtems.org<mailto:chrisj at rtems.org>>
Thank you for your help Chris, I did what you said and it worked. However, I learned that Qt Applications works with X11 libraries in systems like Rtems. And I have to compile the nxlib library for raspberrypi BSP in the rtems-graphical-toolkit for X11. 'graphics\nxlib.bset' in rsb can not be build as mentioned in "https://lists.rtems.org/pipermail/devel/2015-August/012358.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.rtems.org_pipermail_devel_2015-2DAugust_012358.html&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=2qOzfS7qOLo1pWDBn2daTfb11BT4SII6DAGj7Nybgz0&s=FP3leA0B8WdfvIUwiGG0f2VRmehMyQCINAcYMEOWL8k&e=>". I understand that the nxlib is included in microwindows library anymore, but when I build 'graphics/microwindows.bset', will I also build nxlib?. BSP 's X11 header files and so on. How do I add X11 header files to BSP and other necessary files? What should I do at this point?
Best wishes,
Emre
2018-05-01 3:22 GMT+03:00 Chris Johns <chrisj at rtems.org<mailto:chrisj at rtems.org>>:
On 01/05/2018 02:49, Emre Cetin wrote:
> Hello everyone,
Hi and welcome.
> I have a Rtems project with Raspberry pi, I need to compile a simple QT program.
> I tried to run this project on Beaglebone Black, but it may not be as fast as it
> should be, it seems easier on Rpi. And I work on the Rpi 1 model B. In the last
> few days I am trying to establish the necessary libraries for QT, but I have not
> been successful.
This sounds like an interesting project.
> I've been working on Rtems-Graphical-Toolbase, but I have not
> been successful in compilation. I tried a lot of ways but I do not know how to
> load libraries manually yet, I am new to embedded systems.
Welcome to embedded and embedded real-time software.
>
> I finally used these instructions, it seemed the easiest way to me;
>
> (in right directory)
> ../source-builder/sb-set-builder \
> --prefix=$HOME/development/rtems/compiler/5 \
> --rtems-bsp=arm/raspberrypi \
> --log=graphic-build-log.txt \
> --with-rtems-bsp=raspberrypi \
> --pkg-tar-files \
> graphics/freetype2.bset \
> graphics/libjpeg.bset \
> graphics/libpng.bset \
> graphics/libtiff.bset \
> graphics/t1lib.bset \
> graphics/microwindows.bset
>
> RTEMS Source Builder - Set Builder, 5 (f3b1700dfd4d)
> Build Set: graphics/microwindows.bset
> Build Set: graphics/freetype2.bset
> config: graphics/freetype-2.4.10-1.cfg
> package: freetype-v2.4.10-arm-rtems5-1
> error: hash: freetype-2.4.10.tar.gz: insecure: md5
> Build FAILED
>
> It seems that new packages are causing problems, and I do not know how to update
> the codes. Can you give me some advice?
A change went into the RSB in October last year to stop using the MD5 and SHA1
checksums as they are insecure. The ticket that covered this issue is:
https://devel.rtems.org/ticket/2536<https://urldefense.proofpoint.com/v2/url?u=https-3A__devel.rtems.org_ticket_2536&d=DwMFaQ&c=2do6VJGs3LvEOe4OFFM1bA&r=dbavT-WIJ4nBfQFKYnKdAD52Vyq3ZXSzrL9TAm21lZI&m=2qOzfS7qOLo1pWDBn2daTfb11BT4SII6DAGj7Nybgz0&s=W5nqzhQZQ8MD2Qny_KmidQ3uYRpLeCKJeVIEUl3iORE&e=>
It would seem some packages were missed and they need a better checksum. Could
you please reopen the ticket and indicate the issue you have by pasting in the
above output?
FYI the fix is easy, run a sha512 command on your host on the file or patch
which should be in the `sources` or `patches` directory and then update the line
in the related file. The freetype config file is:
rtems/config/graphics/freetype-2.4.10-1.cfg
On the line starting with `%hash` change `md5` to `sha512` and paste in the
SHA512 checksum.
I see ...
libjpeg-9a-1.cfg
libpng-1.5.24-1.cfg
libpng-1.6.21-1.cfg
libtiff-4.0.2-1.cfg
libtiff-4.0.6-1.cfg
microwindows-0.93-dev-1.cfg
t1lib-5.1.2-1.cfg
... are still using MD5 and will need updating.
We welcome patches, it is often the fastest way to get something like this fixed. :)
Thanks
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20180501/5efd719b/attachment-0002.html>
More information about the users
mailing list