texttools + links2
As you maybe know I’m currently working on the book about texttools. I’d like to include a chapter with some details on terminals. But documentation about raw-, cooked-queue and so on sucks^Wdoesn’t really exist ;-(. The only useful documentation I could find is the Single UNIX © Specification on “General Terminal Interface” and of course sourcecode of texttools working with terminals 8-).
And what I don’t like (hey, this should become a rant 8-)): I’d like to have image-support (which looks really great in “links -driver x”!) in framebuffer-mode, but:
[mika@tweety(545): ~/tmp/links2-2.1pre15]$ ./configure --with-fb --enable-graphics [...] Configuration results: GPM support: NO SSL support: YES Javascript enabled: NO Graphics enabled: YES Graphics drivers: X Image formats: GIF PNG XBM JPEG xterm for OS/2 support: NO
And of course a “ldd ./links” shows that ‘links’ is not compiled against libdirectfb & CO. Grml! Ok, I’ll try to figure it out in the next few days. The duel links vs. w3m is still going on :)
July 9th, 2004 at 15:38
A wild guess: X and directfb support might be mutually exclusive, and since you haven’t explicitly deselected X support, links2 configuration selects X as output driver for graphics support. Without actually having tried this by myself, I would suggest to try out ./configure –with-fb –without-x –enable-graphics.
July 9th, 2004 at 16:00
This has been one of my tries, but:
$ ./configure –enable-graphics –with-fb –without-x
[…]
checking for util/application.h… (cached) no
configure: error: No graphics drivers found.
;-(
July 10th, 2004 at 01:35
Oh, well, it works for me(tm) here on Debian testing on mipsel. Unfortunately, framebuffer on mipsel (SGI Indy) isn’t supported by libdirectfb, and normal fb access shows that there’s no device driver behind /dev/fb0 even though the console is running in framebuffer mode! Weird, weird…