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 options at the top. There is one for
building SWORD as a shared library.
Glad you got it almost working!
Troy
On September 1, 2014 3:33:44 PM MST, Jon Behrens <j...@crimsonthread.com> wrote:
>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 library?
>
>Thanks again
>Jon
>
>
>_______________________________________________
>sword-devel mailing list: sword-devel@crosswire.org
>http://www.crosswire.org/mailman/listinfo/sword-devel
>Instructions to unsubscribe/change your settings at above page
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
