Thanks for the information. I will spend some time to do the experiment. BTW, I just remember there is one time ago a project called Nano-X and its extension NxLib which can emulate X library. Would this work for FLTK? (But unluckily, nano-X is dead....)
Jacky 於 13/1/2010 21:10, MacArthur, Ian (SELEX GALILEO, UK) 提到: > >> Ian, can you give an advice how to set up fltk using kdrive. >> And especially >> How to set up kdrive? I there any doc, that people can use? >> My intention is >> To switch to kdrive in future.... > > Setting up KDrive is going to be off-topic for this list, and can be > quite hardware specific - but if you google about you will find lots of > info., and the basic Kdrive/tinyX stuff is in recent X.Org releases, so > obtaining the sources and building them is much like any other X server. > > In summary: get a working cross-compiler environment for your target > h/w, then cross-compile X.Org for your target, configuring it if the > xfbdev server and so forth. If your target h/w is powerful enough, you > can probably do all this "native" on the target, missing out the > complexity of cross-compilation... > Then copy the X server stuff onto the target and launch X, and hope for > the best! > > > Getting fltk going was pretty straightforward; the fltk configure script > is not very cross-compiler compatible, so what I did was: > > - configured a fltk-1.1 tree on a standard linux PC, then hand edited > the "config.h" and "makeinclude" files that generated to point at the > cross-compiler environment and header files, and to ensure the types, > sizes, endian-ness etc., were all correct. (e.g. I ran the configure > script on an x86 PC, so that is little-endian, but my target h/w is > big-endian, that sort of thing...) > Both "makeinclude" and "config.h" are fairly human-readable so making > those changes is not too hard. > > - I ran the configure with --disable-gl --disable-shared --disable-xft > --disable-xinerama as I did not think my target h/w would support these > options. Yours might, so some experimentation could be in order. > > - build the fltk libs "as usual", but using the cross-tools. Note that > this often fails when it gets into the "test" folder as it tries to use > the newly-built fluid executable, but that (obviously) will only run on > the target, not on the build host. You can tweak the Makefiles to ensure > that the local build-host version of fluid is called instead, and then > the test files should all build too. > > - copy the statically linked test executables to your target and give > them a whirl - does it work? > > - I stuggled some with font support, and the built-in fallback fonts > were adequate rather than good, so some work on the fonts on your target > hardware might pay divdends! > > > 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 > > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
