---------- Forwarded message ---------- From: Emre Cetin <hsnemrece...@gmail.com> Date: 2018-05-01 19:13 GMT+03:00 Subject: Re: Raspberry Pi Rtems-Graphical-Toolkit To: Chris Johns <chr...@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". 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 <chr...@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 > > 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 >
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
