On Wed, Feb 27, 2013 at 7:05 AM, Troy A. Griffitts wrote:
> Greg,
>
> Can you update the README in the pertinent bindings/ folders to explain
> how to compile the bindings. All the README files seem to be wrong. I
> know you didn't write them, but you've been the most visibly proactive on
> the
Greg,
Can you update the README in the pertinent bindings/ folders to explain
how to compile the bindings. All the README files seem to be wrong. I
know you didn't write them, but you've been the most visibly proactive
on the make system and the bindings lately. :)
Thanks for any help,
Tr
I have further cleaned up the building of the Bindings. They are now
built and installed along with a single command with everything else.
You still specify -DSWORD_BINDINGS="Perl Python" if you want to e.g.
build both language bindings at once. Then just a standard make/make
install at the library
If you're building with CMake you add the flag -DSWORD_BINDINGS="Perl"
to build the Perl bindings. Then after issuing your standard make
command you'll be prompted somewhere in the output with the next step.
After installing SWORD with a sudo make install you need to cd into
bindings/swig/perl and
Speaking of which, are the Perl bindings automatically generated with makes
or are there additional steps required? I've had no success either finding
documentation on generating the Perl bindings or in using them
~A
On Tuesday, August 28, 2012, Greg Hellings wrote:
> For those of you who don't
For those of you who don't follow the SVN commit logs I have just
cleaned up a couple of compile warnings that the Python and Perl SWIG
bindings would throw during the install stage. Most notable changes
are removal of the Traversable() and Index() methods on the
sword::SWKey class. If you have cod
