[sword-devel] compiling on Windows

Chris Little chrislit at crosswire.org
Sat Oct 3 08:58:16 MST 2009

Matthew Talbert wrote:
>> I am not a programmer ( I'm a wanna be) but have access to MS Visual Studio
>> 6, 2005 & 2008, so options 1 and 3 would be the most beneficial for me.  I
>> think having all of these options documented on the wiki as David Haslam has
>> suggested would be valuable.
> Feel free to put this on the wiki :)
> 3 is not possible with MS Visual Studio. I don't even know what it
> involves except a Borland Compiler.
> For 1, follow these steps:
> 1. Download http://www.crosswire.org/ftpmirror/pub/sword/source/v1.6/sword-1.6.0.tar.gz
> 2. Unpack it somewhere with something like 7zip
> 3. With Visual Studio 2008, open sword-1.6.0/lib/vcppmake/vc8/libsword.proj
> 4. Compile.
> 5. Open sword-1.6.0/utilities/vcppmake/utilities.sln
> 6. Compile.

Steps 3 & 4 are not necessary since the utilities solution includes 
libsword. With SVN prior to yesterday, it was necessary to build the 
solution twice to get it all compiled correctly. Now it has project 
prerequisites set correctly and that's not necessary. Presumably people 
compiling on their own would be more interested in recent SVN than a 
released tarball anyway.

> I do not know much about compiling with ICU and/or clucene with Visual
> Studio. Someone else will have to provide that part of the
> instructions.

Building utilities without ICU is not supported in the VC++ solutions 
(and I can conceive no reason why it should be). So ICU will have to be 
gathered (either from an official release, our icu-sword SVN repo, or 
our icu-sword tarball) and compiled (separately).

Without ICU, the utilities won't build or run.


More information about the sword-devel mailing list