[sword-devel] Python and swig

Bill Burton bburton at mail.com
Sun Feb 4 14:02:38 MST 2007

Hello Jason,

On 2/1/07, Jason Turner <lefticus at gmail.com> wrote:
> I recently worked on the swig bindings themselves, but I agree the
> build process is pretty broken. I modified the .i files, but left the
> build process how it was, focusing instead on the visual studio
> related files for building the bindings with VS.net.

It's good to hear about someone else working on the SWIG bindings.

I've spend quite a bit of time updating the bindings to work with Ruby
and would like to submit a patch.  All my changes are conditioned with
#ifdef's so it shouldn't affect any other language bindings.  However,
it would be helpful if others can test their languages to ensure
everything still works the same way it did previously.

> If anyone is interested in cleaning up the building of bindings, let
> me know, I'd be happy to test and commit the patches.

One thing that would make the process easier on (Unix/Linux at least)
for users building from a released version of Sword is when the
tarball for the next release is created, to update
bindings/swig/package/configure.ac with the release Sword version and
then run ./autogen.sh to create the configure script.

A second thing that should be done is to put a README file in the
bindings/swig folder explaining how to build, link and install the
bindings for each supported language.  Either of these two things
would have saved me a lot of time figuring out to to build the
bindings for any of the existing languages.

One thing I was wondering was the reason for the package folder under
bindings/swig and why all the .i files are copied there instead of
just referencing them in the bindings/swig folder?

May God bless His Word,

> God Bless
> -Jason
> On 2/1/07, Pierre Amadio <pierre.amadio at libertysurf.fr> wrote:
> > Hi there
> >
> > On Tue, Jan 30, 2007 at 10:27:27AM +1100, Ben Morgan wrote:
> > >
> > > To get all book names and chapter counts in old and new testaments:
> >
> > Thanks a lot, things are much more clear now :)
> >

More information about the sword-devel mailing list