Hi, I have finally taken the time to make dillo run on my ipaq. Screenshot: http://www.tzi.de/~akemnade/dillo-ipaq.png The big pitfall here is if you don't enable Xft/freetype in your fltk build, you can screw up things. fltk does not get the default fonts from the xserver on the ipaq, so due to missing error checking in fltk, dillo crashes when the first label gets rendered. But I guess, without freetype you won't get nice fonts anyway... dillo/dw does not need to be patched for that. fltk needs a bit of tweaking, I'll look if it is solved in the current version (I'm still using that r5917 snapshot). Greetings Andreas Kemnade
Hi Andreas, 2008/2/8, Andreas Kemnade <akemnade@tzi.de>:
Nice work! Do you think to create a OpenEmbedded package? Please send this email at OpenEmbedded and GPE mailing list. I think more people will be interest on this.
Greetings Andreas Kemnade
Cheers, Alan
Hi, On Sat, 9 Feb 2008 12:57:33 -0300 Jorge Arellano Cid <jcid@dillo.org> wrote:
Please excuse my lack of knowledge on the iPAQ. Whad does it involve to get dillo2 running on it?
You need somehow a build environment for it. mainly it is about compiling binutils and gcc with --target=arm-linux and installing the familiar packages (including dev-packages) for the required libraries into the search path of the compiler. And a pkg-config with the correct paths compiled in is also helpful (name it arm-linux-pkg-config) And then it is time to compile fltk, dw and dillo with ./configure --host=arm-linux and pay attention that it uses correct paths for every library. And then it is the usual make && make DESTDIR=/somewhere/ install for dillo2. In /somewhere/ you can build a tarball of the installed files and unpack it on the ipaq. I have not looked into package creation yet, but the packet format looks the same as for debian just with another suffix (an ar archive which contains a data.tar.gz (with the real data, a control.tar.gz which some control information like dependencies and install scripts) and another file used as a marker, older versions of familiar seem to bind the three files together as a gzip'ed tarfile). But I'll try to find something out about it. Greetings Andreas Kemnade
participants (3)
-
acassis＠gmail.com -
akemnade＠tzi.de -
jcid＠dillo.org