The X/Escher peers for inclusion in Classpath. After some email exchange with Mark I think it would be best to handle the dependency on Escher just as we handle other dependecies on external libs (GTK, Qt). The only problem beeing this lib is Java, and I have no clue how to teach that to the autotools. Maybe someone has an idea? A --with-escher-jar=/path/to/escher.jar option would be a start. Also, we need to exclude the X peer classes from build when no such jar is found.
Trying out the peers: Escher needs to be in the bootclasspath. The current JAR can be found here (older versions won't work): http://kennke.org/~roman/escher-0.2.3-pre.jar Before you start you might have to: xhost +localhost I think authentication doesn't work right now with Escher. My script for starting the X/Escher peers looks like this: #!/bin/bash cacao -Xbootclasspath/p:/home/roman/workspace/escher \ -Dawt.toolkit=gnu.java.awt.peer.x.XToolkit $@ Have fun. (I'll write a ChangeLog when I other somebody else figured out the autoconf mess). When hitting any immediate problems, please ping me. /Roman -- “Improvement makes straight roads, but the crooked roads, without Improvement, are roads of Genius.” - William Blake
xescher.tar.gz
Description: application/compressed-tar
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
