> Observation: > - The libX11 library compiled for ARM are present in the > embedded system with a custom Xorg. > - The device uses Framebuffer video driver (NOT DirectFrameBuffer). > - I do not make use of XFT.
Given the choice, I would always use XFT rather than making do with the Xlib font handling. > - On device (board), there are no fonts or libraries locally > on the device system. I don't understand what you are telling us here: Are you saying there are no fonts installed on the target device? Where do you expect the Xserver to get its fonts from? You say the fltk-2 build did work? If so, where did it load fonts from? > - The compilation of fltk, was made with flags: --disable-gl > --disable-xdbe --disable-xft --enable-shared I would try and enable XFT, and I would not bother with shared linking of the fltk libs. The savings that makes are often small, or non-existent, in most cases. Why did you opt for shared linking? Is there some specific reason? > - On the enbedded device, i too use Xorg and libX11 shared > library, libfreetype, libXfont, libXau and libXdmcp. > - The compilation of code was made com shared library libX11 (-lX11). > - When i change the string to empty spaces " ", the > strange characteres are displayed too. That sounds like something bad is happening to the font rendering. Can you see the log file the Xserver generates at runtime? What errors or warnings is it showing? > * This problem happen, because had no fonts on the locally > embedded system, at runtime ? An Xserver needs to get its fonts from somewhere (though some do have built-in fonts) so it needs either to have fonts it can access locally, or it needs a fontpath to somewhere on the network it can load from, or...? > * I thought about encoding, but this would not affect the > local compilation x86 too ? Langauge encoding or...? I'm not sure I understand what you are telling us here... Fltk-1.3 usese utf8 for strings, so shouldbe relatively immune to language settings and etc. > * This is a normal situation, using a compilation libfltk and > libX11 with uClibc ? I haven't done a build against uclibc in a long time, but it ought to work OK. I don't know of any reason why it would not. I mainly use newlib for embedded devices, though if your target is linux, uclibc is probably fine too, or maybe even dietlibc? Anyway, here's a thing to try: can you build the fonts demo (fonts.cxx) from the test folder and run that on your target? If so - how does that go? Compare with what the fonts demo does on your host system - perhaps we can learn where the problems are... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
