X lib support for embedded systems.

Piotr Gluszenia Slawinski curious at bwv190.internetdsl.tpnet.pl
Wed Aug 11 00:16:35 PDT 2010

> Ok its like this:
> Our application was developed using fltk-1.3.x. We have lots of existing code that depends on fltk.
> But the person who decided to use fltk-1.3 was really a moron.
> Because, fltk-1.3 was modified by nano-X people to use nxlib interfaces, and all to test the nano-X (x server type) library.
> This was a few years back.
> Now we need a change in fltk. fltk-1.3 has latin1 encoding support and we need our application to internationalize.
> Now for the same we have an answer with fltk-2.0. It supports utf-8. Also note that all of the fltk is built and tested with X11.
> The problem is if I use the same setup, replace fltk-1.3 with fltk-2.0, I need to do lots of changes in nxlib and nano-X, for which I do not have enough time and also it is risky.
> So I think that the easiest solution would be have X11 running on the system directly. So that fltk-2.0 runs without any problem.
> Do you follow?

which architecture and video you are using?
there are few distros optimised for size, if you want something ready,
or you can just use i.e. gentoo to build packages, and then copy those 
packages to your embedded system image manually, or using simple script
utilising dependency list dump...

you can get few megabytes extra by compiling everything against uclibc, 
but you have to either make sure to use nptl branch of uclibc (and have
your arch supported) or make sure just linux threads are used by your apps 
(no nptl). you can get few extra hundreds of kb by using either upx on 
binaries , or even over 50% size reduction by using i.e. squashfs
to compress library dirs, binaries, and all other read-only stuff.


More information about the xorg mailing list