Troy,
I did some more thinking on it last night. I didn't want to accept the offer
unless I'd thought it over. I think I'd be willing to review patches and
such and watch the list for questions and write documentation. I'm not very
familiar with Sword yet, but I'm about to become familiar on a pr
Andrew,
We would be very interested in any contributions you might have.
Currently, I'm not sure if we have anyone who will admit to owning the
swig bindings. There are a few projects who use them, and we get
contributions now and again, but it would be really nice if someone who
is cu
Thanks, that got me started thinking in the right direction. There's one
detail I neglected to mention: I'm doing this on Mac OS X.
Here's what ended up working for me:
cd bindings/swig/package
vim autogen.sh
Here I edit the file so that cp does not use the -a option, which isn't
valid in the B
Hi,
I had to install libtool and swig before this.
cd bindings/swig/package
./autogen.sh
./configure
make
cd perl
make install
At least that did it for me (after several tries :). The build system looks
kind of broken to me, though.
in swig/examples/ is a short example how the swig bindings cou
I was interested in attempting to build the SWIG bindings for Sword in order
to use the Sword API in conjunction with a Perl project I'm working on.
However, I'm having some trouble figuring out how to build them. They don't
build with the regular ./configure as far as I can tell and
bindings/conf
I was interested in attempting to build the SWIG bindings for Sword in order
to use the Sword API in conjunction with a Perl project I'm working on.
However, I'm having some trouble figuring out how to build them. They don't
build with the regular ./configure as far as I can tell and
bindings/conf
