[bt-devel] Qt Only
Greg Hellings
greg.hellings at gmail.com
Mon Feb 23 11:02:38 MST 2009
On Mon, Feb 23, 2009 at 3:07 AM, Eeli Kaikkonen
<eekaikko at mail.student.oulu.fi> wrote:
> Quoting Greg Hellings <greg.hellings at gmail.com>:
>> Currently the build stops at cswordsetupinstallsourcesdialog.h when it
>> can't find sword/installmgr.h, which is thoroughly entrenched right in
>> the middle of my sword include files. Not sure why it's not finding
>> that particular file - any ideas?
>>
>
> Not any other idea than the usual one: do you have had several sword
> versions installed or have it in several places so that cmake finds it in
> different place than where you are looking at?
I have only one location with SWORD installed - however, it appears
that the problem only arises because I have SWORD installed to a
location where no other libraries that BibleTime depends on are
located. Scouring through the BibleTime code, almost all of the SWORD
headers that are included are referenced directly as "#include
<swmgr.h>" and the like, without the sword/ prefix. This, of course,
mandates that CXXFLAGS have the item -I/usr/local/include/sword or
wherever the SWORD headers are placed. In my case, they are located
at /opt/manual/include/sword. However, in a few cases, including
cswordsetupinstallsourcesdialog.h and btsourcearea.cpp/.h, you find
"#include <sword/installmgr.h>" - normally, if SWORD is installed in
the same directory as many other libraries that BibleTime uses, one
would also have a -I/usr/local/include, which would cause the
discrepancy to be overlooked, since references to either
<installmgr.h> or <sword/installmgr.h> would both be reachable.
However, in my case, since SWORD is the only manually installed
library that BibleTime is picking up, there is no
-I/opt/manual/include, so the references to <sword/installmgr.h> are
not being resolved.
I haven't checked all the other SWORD headers to see if they are
sometimes referenced as sword/*, though I did remove the "sword/" from
the three files I mentioned above and compile went cleanly after that.
With one small change to the CMakeList.txt file to install the binary
to the proper place in the bibletime.app bundle folder, I was able to
get Bibletime up and running on my system. It properly detects a KJV
module I installed using SWORD's command-line tool, but BibleTime's
install manager brings up a window claiming that it's installing a
module and never seems to make any progress in the installation. I'm
going to try leaving it running for a while to see if it is just
progressing very slowly. However, the system is up and running with
only the compile-time modification I mentioned above with the include
files.
--Greg
--Greg
More information about the bt-devel
mailing list