Re: [sword-devel] Compiling SWORD API using MinGW

2008-04-06 Thread David (Mailing List & Spam Address)
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-04-06 Thread Chris Little
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-04-06 Thread DM Smith
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-04-06 Thread Eeli Kaikkonen
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-04-06 Thread Chris Little
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-04-05 Thread Troy A. Griffitts
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-04-05 Thread Chris Little
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-02-13 Thread Ben Morgan
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

Re: [sword-devel] Compiling SWORD API using MinGW

2008-02-13 Thread Mico Siahaan
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.

Re: [sword-devel] Compiling SWORD API using MinGW

2008-02-05 Thread Troy A. Griffitts
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