Waf should be choosing webkit-editor by default *unless* you're passing
'--enable-webkit2'. (we didn't port the editor to WebKit2)
If it's not default try passing '--enable-webkit-editor'
The simplest way to know what the options are is to just look at this
python file: https://github.com/crosswire/xiphos/blob/master/wscript
Also Unit193 on Freenode has quite a bit of experience compiling Xiphos on
Debian, so he'd be worth pinging for up to date info/help. (He is usually
available in #xebian or try https://launchpad.net/~unit193)
On Mon, 19 Sep 2016 at 17:57 Peter von Kaehne <ref...@gmx.net> wrote:
> Debian testing has seemingly done away with gtkhtml. Xiphos compiles
> and works just fine though with the webkit based editor. Unfortunately
> the webkit based editor is not an automatic choice in absence of the
> gtkhtml library, but needs to be called as an option.
> My questions:
> 1) Can waf get easily fixed to incorporate an automatic search for
> webkit-editor as an alternative to gtkhtml-editor?
> 2) Is there an way of making waf list all options available for
> compiling - it took me a considerable time to figure out what to do
> when the ordinary compile failed.
> xiphos-devel mailing list
xiphos-devel mailing list