<html><body><div>Hi Pavel Pisa,<br><br>Thanks for your reply with patience.<br><br>In order to confirm that I didn't mess up the path or something, I've cleaned up and re-built everything.<br><br>The problem is so weird because I had set the path correctly. What I learned from the log is that, libraries libjpeg , libfreetype, libpng, libt1, libtiff, libnanox, libX11 has been successfully compiled and installed, which cannot be found during the compilation of microwin and fltk. Only few executable has been built for microwin : convbmp, makebmp, convbdf. I can hardly tell anything from the log the reason why it can't find the installed libraries. I'm trying to look into the <br><br>My text editor hide the files .a automatically so I didn't see the installed libraries for microwin until I open the folder in browser ... Yes all has been compiled and installed successfully except for fltk.<br><br>As the excutables cannot be compiled, I don't have any of those demos. I'm trying the rtems test framework and I'll update later.<br><br>As for the harmless <span class="body-text-content">freetype2 error,</span> the removal of non-existing directory is not a bug. It's used to ensure that we have removed the internal for old version.<br><br>Thanks for your patience.<br><br>Regards<br><br></div><div><br>On Apr 01, 2015, at 04:52 PM, Pavel Pisa <ppisa4lists@pikron.com> wrote:<br><br><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch"><span class="body-text-content"><span class="body-text-content">Hello Qiao Yang,<br><br>thanks for the progress report.<br><br>On Wednesday 01 of April 2015 01:42:04 QIAO YANG wrote:<br></span></span><blockquote class="quoted-plain-text" type="cite">I've cleaned and recompiled it with the latest rtems4.11 and gtk from</blockquote><blockquote class="quoted-plain-text" type="cite">github, and also the microwin and the nxlib from alex's fork, apply the</blockquote><blockquote class="quoted-plain-text" type="cite">microwin patch manually(as for the commit number doesn't exist). From the</blockquote><blockquote class="quoted-plain-text" type="cite">build log, It seems that many tests have failed for microwin due to</blockquote><blockquote class="quoted-plain-text" type="cite">"undefined reference". The full build log is here the link to my evernote.</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite"><a href="https://www.evernote.com/shard/s271/sh/de7200c2-721b-47e5-b3b4-924b33483ec2/bb22975157ac49766edc434ec2af9e0a" data-mce-href="https://www.evernote.com/shard/s271/sh/de7200c2-721b-47e5-b3b4-924b33483ec2/bb22975157ac49766edc434ec2af9e0a">https://www.evernote.com/shard/s271/sh/de7200c2-721b-47e5-b3b4-924b33483ec2/bb22975157ac49766edc434ec2af9e0a</a></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><span class="body-text-content"><span class="body-text-content"><br>As for Microwindows, we have successfully builded Microwindows<br>and used /opt/rtems4.11/.... installed libraries for more own<br>test on x86 and ARM even our complete production ARM RTEMS 4.10<br>application could be compiled against 4.11 with actual Graphics Tool Kit.<br><br>But there may be some demos in Microwindows sources which do not build<br>according for RTEMS (I will recheck with actual RTEMS sources).<br>There is list of executables which as been successfully compiled<br>in my Microwindows build<br><br>rtems-graphics-toolkit/build/microwin/src/bin<br><br>move world nxmag bmpdemo makebmp nxkbd convbdf setportrait nxview npanel slider demo polydemo mdemo mwdvetest.res mine landmine arcdemo mtest2 <br>grabdemo tux tuxchess fonts fontdemo setselection convbmp pcfdemo logfont nxclock mwdvetest malpha ntetris nsaver monobitmap nxev demo2 dashdemo <br>blitdemo tsdemo getselection nxeyes demo5 nxlsclients nxcal launcher mtest nxscribble rgndemo t1demo composite snap_ppm ftdemo demo6 nxroach<br><br>The malpha is good/know to work candidate for testing<br><br>I run it by<br><br> qemu-system-x86_64 -gdb tcp::1234 -enable-kvm -kernel ./malpha \<br> -vga cirrus \<br> -net nic,vlan=0,model=e1000 -net user,vlan=0 \<br> -append "--console=com1"<br><br>But you can/should use standard RTEMS testing framework which can found<br>in<br><br> <a>git://git.rtems.org/rtems-testing.git</a><br><br><br>Back to your log<br><br>make[3]: *** No rule to make target '-ljpeg', needed <br>by '/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/microwin/src/bin/nxscribble'.<br>make[3]: *** No rule to make target '-lfreetype', needed <br>by '/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/microwin/src/bin/nxscribble'.<br>make[3]: Target 'all' not remade because of errors.<br>make[3]: Leaving directory '/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/microwin/src/demos/nxscribble'<br>/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/microwin/src/Makefile.rules:527: recipe for <br>target 'subdir-/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/microwin/src/demos/nxscribble/' failed<br><br>I see some problems caused problem to find some libraries.<br>You should find these libraries installed in /opt/rtems4.11<br>after<br><br> ./do_it -A<br><br>/opt/rtems4.11/i386-rtems4.11/pc686/lib/libjpeg.a<br> libpng.a -> libpng15.a<br><br>etc.<br><br>If they are not there then it is necessary to find why they have not been<br>installed. They can be copied there from Graphics Tool Kit build manually<br>to check the rest of the build. But the problem should be resolved.<br><br>This problem seems to propagate to other components as well.<br><br>But generally, Microwindows libraries (not demos) seems to be fully compiled.<br><br>Real problem appears in the build of FLtk<br><br> /home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/fltk-1.3.0/<br><br>But even there many of tests build<br><br>Compiling Fl_PNG_Image.cxx...<br>Compiling Fl_PNM_Image.cxx...<br>/home/yangqiao/development/rtems-386/compiler/4.11/bin/i386-rtems4.11-ar cr ../lib/libfltk_images.a ...<br>=== making test ===<br>Compiling unittests.cxx...<br>Linking unittests...<br>Compiling adjuster.cxx...<br>Linking adjuster...<br>Compiling arc.cxx...<br>....<br>Compiling buttons.cxx...<br>Linking buttons...<br>Compiling cairo_test.cxx...<br>Linking cairo_test...<br>/home/yangqiao/development/rtems-386/bsps/4.11/i386-rtems4.11/pc386/lib/libnano-X.a(image_jpeg.o): In function `GdDecodeJPEG':<br>/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/microwin/src/engine/image_jpeg.c:118: undefined reference to `jpeg_std_error'<br><br>Yet there seems to be problem with finding JPEG library.<br><br>As for Fluid (graphical GUI designer tool), it fails but that is expected, because<br>it has no purpose to be build for RTEMS. There is required native Linux executable to<br>be build even for RTEMS target design<br><br>Compiling ../fluid/fluid.cxx...<br>Linking ../fluid/fluid...<br>../fluid/fluid.o: In function `save_template_cb(Fl_Widget*, void*)':<br>/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/build/fltk-1.3.0/test/../fluid/fluid.cxx:237: undefined reference to `template_panel'<br><br>But generally, I have newer used FLtk with RTEMS and I expect that there<br>is quite huge amount of work left to make it usable on RTEMS.<br>It requires to compile (or use actual RTEMS 4.11 dlopen) to include<br>X style window manager in actual running RTEMS system to be able to manage<br>FLtk windows.<br><br>But that could be great target and usesfull target for your<br>or some others work<br><br>===========================================================<br>BUT GRAPHIC TEST LOADED BY NEW DLOPEN COULD BE GEAR AND<br>REALLY USESFULL TARGET FOR YOUR OR SOME OTHERS WORK<br>===========================================================<br><br>Because today it is possible to build base RTEMS system<br>with drivers and may it be base Graphics Tool Kit<br>libraries compiled in basic system image and then load<br>all test dynamically under some scrips requests and prepare<br>some guidepost type gui for manual iteration through tests.<br><br>On Wednesday 01 of April 2015 01:42:04 QIAO YANG wrote:<br></span></span><blockquote class="quoted-plain-text" type="cite">Here is an error of freetype</blockquote><blockquote class="quoted-plain-text" type="cite">at line 2119 of build log:</blockquote><blockquote class="quoted-plain-text" type="cite">rmdir: failed to remove</blockquote><blockquote class="quoted-plain-text" type="cite">‘/home/yangqiao/development/rtems-386/bsps/4.11/i386-rtems4.11/pc386/lib/in</blockquote><blockquote class="quoted-plain-text" type="cite">clude/freetype2/freetype/internal’: No such file or directory</blockquote><blockquote class="quoted-plain-text" type="cite">/home/yangqiao/development/rtems-386/rtems-graphics-toolkit/freetype-2.4.10</blockquote><blockquote class="quoted-plain-text" type="cite">/builds/unix/install.mk:31: recipe for target 'install' failed make:</blockquote><blockquote class="quoted-plain-text" type="cite">[install] Error 1 (ignored)</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">I've read that the freetype2 didn't use internal folder anymore after a</blockquote><blockquote class="quoted-plain-text" type="cite">release of 2012. It's not a fatal error here and it's ignored. But I wonder</blockquote><blockquote class="quoted-plain-text" type="cite">if the tests still use some headers from it which may cause the massive</blockquote><blockquote class="quoted-plain-text" type="cite">undefined references ( I know little about the detail, just a personal</blockquote><blockquote class="quoted-plain-text" type="cite">suspicion).</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">As for the rest errors, you may know them much better :), I'll also try to</blockquote><blockquote class="quoted-plain-text" type="cite">find out .</blockquote><span class="body-text-content"><br>Please, try to check what is a problem and send report.<br><br>Try to correct freetype-2.4.10/builds/unix/install.mk to resolve the<br>error and run build again. You should have all sources<br>in GIT repositories so your modification are<br>easily found by<br><br> git diff<br> (cd microwin && git diff)<br> (cd nxlib && git diff)<br><br>Best wishes,<br><br> Pavel<br><br><br><br></span></div></div></blockquote></div></div></body></html>