Looking at the clucene project file here:
http://crosswire.org/svn/biblecs/branches/BCB5/clucene/clucene.bpr
it looks like we define:
MAX_PATH=256;UNICODE;_WIN32;_CL_DISABLE_MULTITHREADING;LUCENE_ENABLE_REFCOUNT
Just as a general note, whatever you define when you build clucene
itself, should
>
> In the end, I really think you want TCHAR to be wchar_t, even if the
> other way is possible. This is because I believe that defining TCHAR
> as char for clucene will force it into ANSI mode instead of Unicode,
> which means indexing, etc may not work for non-latin texts.
>
So is it posible
>
> 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
On Sat, Mar 7, 2009 at 11:52 PM, Matthew Talbert wrote:
> I misread that sword actually compiled. Upon closer look, I see it
> failed with precisely the same errors I expected.
>
> Greg, I would be interested in knowing whether BT is using clucene
> compiled without Unicode support. The easiest wa
I misread that sword actually compiled. Upon closer look, I see it
failed with precisely the same errors I expected.
Greg, I would be interested in knowing whether BT is using clucene
compiled without Unicode support. The easiest way to do this is to
look in the pre-processor definitions and see i
On Sat, Mar 7, 2009 at 11:48 PM, Greg Hellings wrote:
> MMital,
>
> I had the same problem linking CLucene into Bibletime. The solution
> was simple, although not self-evident. I'm going to guess that you
> are building the CLucene library with the provided project file in
> clucene-core-0.9.21b
MMital,
I had the same problem linking CLucene into Bibletime. The solution
was simple, although not self-evident. I'm going to guess that you
are building the CLucene library with the provided project file in
clucene-core-0.9.21b\win32. This is, strangely, not an overly
effective way to do it.
Hi,
Made a little progress with this. A majority of the 133 errors related to
TCHAR disappeared after I added:
#define TCHAR char
I added this in StdHeader.h line 177
//always include replacement, some missing tchar defines
#include "CLucene/config/repl_tchar.h"
#define TCHAR char
I wish I could help, but I have not done much with clucene. What I can say
is if you get it to work, can you tell me how you did it? I want to build
clucene for wince and I am guessing you will have me half way there once you
get it worked out yourself :-P
In Christ,
David Trotz
On 2/2/09 11:05