I found it. (at least what I had to do to get sword producing a .so file.
Open usrinst.sh and comment out the following line by putting a # at the start:
OPTIONS="--disable-shared $OPTIONS"
to:
#OPTIONS="--disable-shared $OPTIONS"
This should mean you get a .so created.
On Tue, Sep 2, 2014 at 12
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
