[sword-devel] compiling sword library with CLucene
Troy A. Griffitts
scribe at crosswire.org
Sun Mar 8 08:55:40 MST 2009
Looking at the clucene project file here:
it looks like we define:
Just as a general note, whatever you define when you build clucene
itself, should also be defined when you build any app that links to
clucene. Otherwise, your headers may define different object sized and
export different method signatures-- or even entire methods (beware of
_DEBUG in clucene).
Hope this is useful.
Matthew Talbert wrote:
>> The default build that comes out of the CMake file has WIN32,
>> _WINDOWS, _DEBUG, CMAKE_INTDIR defined for the CLucene build file that
>> I'm using, and that's it. However, when looking through
>> clucene-config.h and CLConfig.h in the CLucene build directories, it
>> appears that they default to using the UNICODE build and that you
>> define _ASCII if you want to force the library into ASCII mode. So I
>> believe that we're using a Unicode-enabled build.
> Greg and I discussed this some more, and I'm not quite as sure as I
> was, but he's currently having some (possibly unrelated) issues with
> clucene so we can't quite nail it down yet. If there are any experts
> on any of this (I'm assuming there aren't from the lack of response to
> previous questions, although I'm curious as to how BibleCS overcomes
> these issues), then we'd like to hear from them.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel