Hello all,
Today is Labor Day (in the US), and I haven't heard anything about my
thread "Building Python binding to Sword on Windows returns exit code 1"
since around Memorial Day (May 26) weekend. I'm disappointed by this,
because I can't continue working on the Bible software I was attemptin
Yes, usrinst.sh configures the build with options most convenient for a SWORD
engine developer (well, what I consider most convenient) and that is to build
SWORD for static linking so you never accidentally test against some other
libsword on your path.
Edit usrinst.sh and have a look at the op
Thanks to Troy's help, I've got Sword installed, modules downloaded and the
cmdline example now works.
I still don't have a libsword.so which is needed for the C# bindings
project to run.
I've got a libsword.la and a libsword.a
Is there a compiler switch I need to set to generate the .so libra
Hi Isaac,
On August 31, 2014 1:49:11 PM MST, Isaac Dunham >
>> While installmgr previously did not output proper errors when it
>could not
>> write to the output path, this is no longer the case for a while now.
>
>Might I ask when this was fixed? I ran into it with 1.7.3.
I would need to look
