building Verity on Linux Mint

[Daniel Owens]

I am trying to build Verity on Linux Mint 12 KDE and running into an error on make:

*****
In file included from /usr/include/CLucene/config/compiler.h:40:0,
from /usr/include/CLucene/StdHeader.h:17,
from /usr/include/CLucene.h:11,
from netanalyzer.h:4,
from searchdisplaybrowser.cpp:6:
/usr/include/CLucene/config/CompilerGcc.h:12:68: fatal error:
CLucene/clucene-config.h: No such file or directory
compilation terminated.
make: *** [searchdisplaybrowser.o] Error 1
*****

I have libclucene0ldbl and libclucene-dev installed. Anyone else have an idea about how to fix this?

Daniel

[Troy A. Griffitts]

The Fedora guys place:

CLucene/clucene-config.h at:

/usr/lib64/CLucene/clucene-config.h
(on a 64bit system; /usr/lib/... on 32bit)

So I needed to add /usr/lib64 to INCLUDEPATH in verity.pro:

INCLUDEPATH += /usr/include /usr/lib64

Not sure where the Mint guys put the file. Maybe you can do the deb
equivalent of:

yum provides */clucene-config.h

and add the discovered path accordingly.

NB: the path is not the immediate folder which contains:
clucene-config.h, but the path immediately above because the include
file is reference by:

CLucene/clucene-config.h

Hope this helps,

Troy

[Daniel Owens]

Thanks! That did the trick. I just had to add /usr/lib.

Daniel

[James Cuénod]

Hey,

Thanks Troy. Yeah, I'm on Fedora and I must admit I'm not sure whether
we've included CLucene correctly or not.
It seems not but I don't know what's wrong - if you have any insight
it would be much appreciated.

Sorry about the issues Daniel.

[Daniel Owens]

No problem. That's part of the process.

I was able to install Troy's patch to allow Verity to access SWORD
modules, and I really hope you consider moving in this direction.

As a testimony from a scholar, in my dissertation work on Psalms I used
Bibledit to translate Book I, adding notes on certain issues as I went
along. I then generated a SWORD module of my own translation from
Bibledit, and I used that as I was working on my chapter on Book I. It
is so convenient (and cool!) to be able to have my own translation and
parsing, etc., next to the WLC, ESV, NET, etc. (and soon the Westminster
Hebrew Morphology) within a SWORD front-end. So if your focus is study
in the original languages, consider the potential of combining the SWORD
Library with Verity's interface. I would have been super happy to have
the versification in the Psalms line up correctly, as yours does. That
was no problem with my own translation, which was based on MT, but when
I add the ESV things don't work as well. What you have done with
parallel display would have removed that headache.

Daniel

[Troy A. Griffitts]

Hey James,

Well, it's kindof an odd thing right now. clucene stable is versioned
at 0.9.x, but many distros have been building the newer thread which
mirrors Java Lucene 2.3.x.

So depending on your distro, you may have one or the other or both. We
check for all of this in our autotools build system (and probably our
cmake system, but I build SWORD with autotools still).

So, you have a couple options.

if you have the Fedora packages installed, you probably have the newer
branch, which also include a pkg-config .pc file. So, if you are happy
only supporting the newer branch, the proper way to build against clucne
would probably to remove completely your INCLUDEPATH and LIBS variables,
and simply add:

CONFIG += link_pkgconfig
PKGCONFIG += libclucene-core

Hope this helps,

Troy