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
Hi,
Can someone help me figure out how to compile sword with CLucene support?
Here are the errors I'm getting.
http://www.swordwarrior.net/CLucene_MSVS.pdf
Thanks a lot,
mmital
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.cro
On Sunday 06 April 2008 05:20:06 pm Chris Little wrote:
> but I don't believe KDE has even been ported to compile
> under MinGW.
As of KDE 4.0 this is no longer the case, KDE will build with mingw /or/
visual studio/visual c++ but the windows port of KDE is still not quite at
the production lev
DM Smith wrote:
> On Apr 6, 2008, at 2:03 PM, Eeli Kaikkonen wrote:
>
>> On Sat, 5 Apr 2008, Chris Little wrote:
>>> Ultimately, I'm hoping (fingers crossed) to get GnomeSword (maybe
>>> even
>>> BibleTime?) building on/for Win32 in a way that it can be distributed
>>> binary-only in a minimal
On Apr 6, 2008, at 2:03 PM, Eeli Kaikkonen wrote:
> On Sat, 5 Apr 2008, Chris Little wrote:
>> Ultimately, I'm hoping (fingers crossed) to get GnomeSword (maybe
>> even
>> BibleTime?) building on/for Win32 in a way that it can be distributed
>> binary-only in a minimal way (that is, without a h
On Sat, 5 Apr 2008, Chris Little wrote:
> Ultimately, I'm hoping (fingers crossed) to get GnomeSword (maybe even
> BibleTime?) building on/for Win32 in a way that it can be distributed
> binary-only in a minimal way (that is, without a huge Cygwin install).
>
> --Chris
It would be good if you succ
Hmm, I'm surprised you had issues with ICU. I tried icu-sword from our
repository and it didn't work, but I'm fairly sure that was because of
recent changes that were my fault. (I'll have to fix that I guess, since
it should also affect Linux builds.) But I used the stock ICU from their
SVN rep
Chris,
I used MinGW to build the swordweb for win32 package on the FTP server.
I had to install a ton of packages. It took me forever to get
everything I needed. I still don't think I got ICU working, so if you
got ICU compiled, maybe we could swap secrets. I'll upload my MinGW
environmen
Has anyone had any luck compiling Sword on MinGW lately?
It worked once upon a time. We even have some Makefile defines specific
to MinGW. And I /can/ get Sword to build (though it has lots of problems
later in the utilities part of the build process that I haven't yet
worked through), but it's
Hi,
I think there is a buildtest.exe generated in the base directory which
you could just run to check the sword is working.
Also, you could try building one of the examples in the examples directory.
God Bless,
Ben
Dear Troy,
I did compile Sword library using Mingw. How to check whether it works
well or not? Because after compiled Sword library, I compiled python
swig binding of Sword. It also run well. But when I tried to import the
binding (Sword.py) and did mgr = SWMgr(), my python interpreter closed.
Mico. Have a look at usrinst.sh. It calls configure with most options
you want. For MinGW, you will most likely want to disable ICU (unless
you can get an ICU devel package, which I have had no luck finding) and
for now, probably clucene support (clucene does compile, so if you
compile and i
Hi, I am new in programming and I tried to compile
SWORD API using MinGW compiler under Windows XP
Professional. What I did:
1. run ./configure
2. run make
then I got this error:
Making all in lib
make[1]: Entering directory
/home/mico/sword-1.5.10/lib'
/bin/sh ../libtool --tag=CC --mode=comp
On Fri, 9 Feb 2007, Chad Johnson wrote:
> Anybody figure this ustdio thing out?
> http://crosswire.org/pipermail/sword-devel/2006-July/024181.html
>
It's ustdio, not lustdio. -l is a program argument and is followed by a
library name, weirdly without a space. Ustdio seems to belong to ICU
library
Anybody figure this ustdio thing out?
http://crosswire.org/pipermail/sword-devel/2006-July/024181.html
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your s
Moses, you can turn icu off in sword by editing usrinst.sh and
commenting out the appropriate line. Then run ./usrinst.sh, then make
Moses Truong wrote:
> OK, I've run
> ./autogen.sh
> And that created the configure files...
> but when I ran
> make
>
> I get the following error:
> make[1]: Enter
you probably have to run sudo apt-get install build-essential
other issues can probably be resolved in #ubuntu on irc.freenode.net
They're pretty good with support for getting your compiler working
On 7/24/06, Moses Truong <[EMAIL PROTECTED]> wrote:
> OK, I've run
> ./autogen.sh
> And that creat
OK, I've run
./autogen.sh
And that created the configure files...
but when I ran
make
I get the following error:
make[1]: Entering directory `/home/moses/sword/trunk'
/bin/sh ./libtool --tag=CXX --mode=link g++ -g3 -O0 -DCURLAVAILABLE -g
-O2 -o buildtest buildtest.o ./lib/libsword.la -lz
g++ -
Moses,
I first do:
./autoconfig.sh
Carefully read the output. It may tell you to concat a file. Don't
remember exactly, but it is something like aclocal.m4.
Then run ./usrinst.sh which will run configure for you.
Hope this helps,
DM
On Jul 23, 2006, at 11:18 PM, Moses Truong wrote:
I'm trying to compile Sword from SVN following instructions from
http://www.crosswire.org/sword/develop/biblecs/svn.jsp
After checking out from https://crosswire.org/svn/sword/trunk (from HEAD
I think - I was using kdesvn)
I tried to run ./configure - but the file does not exist.
I tried to run
Great that's fixed my problem. Thanks. I've compiled sword, but there
remain a couple of problems.
When finally finishing compiling both the i386 and ppc architectures
are specified. It works if I just remove the -arch i386, but I do that
by hand,
/bin/sh ../libtool --mode=link g++ -ftemplate-
Daniel Glassey wrote:
Troy A. Griffitts wrote:
Will,
It might be the version of automake/autoconf that you have on your
system. But since you mention a link error, does that mean that you
are able to run ./configure and make even thought the autogen.sh
script thows these warnings? If so, c
Troy A. Griffitts wrote:
Will,
It might be the version of automake/autoconf that you have on your
system. But since you mention a link error, does that mean that you are
able to run ./configure and make even thought the autogen.sh script
thows these warnings? If so, could you post the link
Will,
It might be the version of automake/autoconf that you have on your
system. But since you mention a link error, does that mean that you are
able to run ./configure and make even thought the autogen.sh script
thows these warnings? If so, could you post the link error? I don't
know much
With that link I get similar errors:
*** Sword build system generation
*** Recreating libtool
libtoolize
*** Recreating aclocal.m4
aclocal
*** Recreating configure
Can't locate object method "path" via package "Autom4te::Request" at
/usr/bin/autom4te line 81.
autoheader: /usr/bin/autom4te failed
Will,
Could you confirm for me that you DON'T have the same issue in the
latest 1.5.8 release candidate, and I'll try to hunt down what changed
since then:
http://crosswire.org/sword/ALPHAcckswwlkrfre22034820285912/alpha/sword-1.5.7.100.tar.gz
-Troy.
Will Thimbleby wrote:
Hi, I have pr
Hi, I have problems when I make sword and also problems with
autogen,sh. Here is the trimmed output from autogen. Are these warnings
a problem, and is there an easy way to fix them? thanks --Will
*** Sword build system generation
*** Recreating libtool
libtoolize
*** Recreating aclocal.m4
acloca
On Friday 08 October 2004 23:42, Brook Humphrey wrote:
> I cant help you out much till mandrake 10.1 is released in the
> next couple [of] weeks.
Mandrake 10.1 (at least, Cooker as of yesterday) seems to ship with:
sword-1.5.7a-1mdk
If I want a later version I typically pull the SRPM, add th
On Friday 08 October 2004 03:47 pm, Troy A. Griffitts wrote:
> Here's what we have on our server, which builds sword
> successfully:
>
> [EMAIL PROTECTED] swordreader]$ autoconf --version
> autoconf (GNU Autoconf) 2.59
>
> [EMAIL PROTECTED] swordreader]$ automake --version
> automake (GNU aut
David Blue,
Here's what we have on our server, which builds sword
successfully:
[EMAIL PROTECTED] swordreader]$ autoconf --version
autoconf (GNU Autoconf) 2.59
[EMAIL PROTECTED] swordreader]$ automake --version
automake (GNU automake) 1.8.3
If you type: ./autogen.sh
in the root of the sword sv
On Friday 08 October 2004 07:44 am, David Blue (Mailing List Addy) wrote:
> On Friday 08 October 2004 09:01 am, Brook Humphrey wrote:
> > I'm not sure exactly what you are doing wrong but sowrd is in mandrake
> > contribs and is included with mandrake now in the distro. It is
> > maintained by myse
On Friday 08 October 2004 09:01 am, Brook Humphrey wrote:
> I'm not sure exactly what you are doing wrong but sowrd is in mandrake
> contribs and is included with mandrake now in the distro. It is maintained
> by myself and buchan milney
Well, yes, but the current bibletime cvs requires sword svn
On Thursday 07 October 2004 09:55 pm, David Blue (Mailing List Addy) wrote:
> Ok, I just got subversion installed and got sword downloaded...now how do I
> get it to compile with Mandrake 10? I changed some symlinks to point to
> automake 1.6 rather than 1.4 and I still get weird errors like,
>
> a
Ok, I just got subversion installed and got sword downloaded...now how do I
get it to compile with Mandrake 10? I changed some symlinks to point to
automake 1.6 rather than 1.4 and I still get weird errors like,
aclocal: configure.ac: 148: macro `AM_CXXFLAGS' not found in library
aclocal: config
I fixed the #ifdef statement to uppercase, and now everything compiles
just fine. Thanks for your help guys!
Kind regards,
Martijn Ruff
--
Romans 11:36
For of Him, and through Him, and to Him, are all things:
to whom be glory for ever. Amen.
>>> [EMAIL PROTECTED] 12-11-03 10:05 >>>
Thanks Ad
Thanks Adam, I'll try this.
I just can't try it right now, since the machine I'm planning to run
sword on is a stand alone machine with no network, and right now I'm at
work.
Daniel,
If this doesn't fix the problem, I'll send you the makefile.
Thanks for all the help,
Kind regards,
Martijn Ru
On 10 Nov, 2003, at 04:37, M. Ruff wrote:
#ifdef unix# include #else# include//
This one is missing# include // This one is also
missing#endif
Seems pretty basic, but now I read this, it's probably the that 'unix'
isn't defined. I wonder why...
If you change #ifdef unix
On Mon, 2003-11-10 at 10:37, M. Ruff wrote:
> Thanks for your quick reaction Daniel,
>
> The reason I thought I needed Makefile.cfg and Makefile.post was that
> the moment I did a 'make' (after a ./configure), make complained it
> missed these two files.
Hmmm, I'm still curious about why it is
Thanks for your quick reaction Daniel,
The reason I thought I needed Makefile.cfg and Makefile.post was that
the moment I did a 'make' (after a ./configure), make complained it
missed these two files.
But okay, I'll try doing it with gmake or automake. Only the version of
automake distributed w
On Fri, 2003-11-07 at 15:23, M. Ruff wrote:
> Hi everyone,
>
> I've been trying to compile the sword API 1.5.6. on an OpenBSD 3.4
> (i386) system, but when I do a './configure' followed by a 'make' , no
> 'Makefile.cfg' and no 'Makefile.post' are created. This will cause
> 'make' to stop. When I
Hi everyone,
I've been trying to compile the sword API 1.5.6. on an OpenBSD 3.4
(i386) system, but when I do a './configure' followed by a 'make' , no
'Makefile.cfg' and no 'Makefile.post' are created. This will cause
'make' to stop. When I use gmake, the compilation starts, but after a
while, tw
This is under Mandrake 8.0, everything compiles fine then this happens...
gcc -I../include/ -D_GNU_SOURCE -DNDEBUG -D_GNU_SOURCE -DNDEBUG -pipe -Wall
-Wno-format -pedantic -pedantic -fomit-frame-pointer -s -O3 -DUSBINARY -m486
-o keytest keytest.cpp -L../lib/ -lsword -lstdc++ -lz
../lib//li
50 matches
Mail list logo
