So I was trying to solve both the "Perl won't install" and the "Python installs to the wrong place" issues. I committed a fix to the Python install (it was previously only installing to /usr/local regardless of the value of CMAKE_INSTALL_PREFIX) but this fix appears to have magically caused Perl to begin installing on my machine.
Peter, can you try and do a new install from the latest versions of SVN HEAD? Perl is still only installing to /usr/local regardless of where I set CMAKE_INSTALL_PREFIX, but I imagine that fix is low priority at the moment as the bindings are not presently packaged by any distributions I am aware of. I would invite distribution maintainers to begin packaging the Python and Perl bindings starting with 1.7.0. I have done lots to clean them up, suppress warnings, and resolve build failures. Packaging the Python bindings would permit packaging of BPBible as well, and also help with keeping the various build options I've created for the bindings clean and tested. --Greg On Sun, Jul 7, 2013 at 3:20 PM, Peter von Kaehne <ref...@gmx.net> wrote: > sword-tools/modules/crossreferences/xreffix.pl without arguments will > test loading Perl Sword bindings > > and in Python: > > Simply run from commandline Python and do "import Sword" and see it fail: > > >>> import Sword > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "Sword.py", line 26, in <module> > _Sword = swig_import_helper() > File "Sword.py", line 18, in swig_import_helper > import _Sword > ImportError: /usr/local/lib/python2.7/dist-packages/_Sword.so: undefined > symbol: u_strFromUTF8_48 > >>> > > > *Gesendet:* Sonntag, 07. Juli 2013 um 19:06 Uhr > *Von:* "Greg Hellings" <greg.helli...@gmail.com> > *An:* "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org> > *Betreff:* Re: [sword-devel] SWORD 1.7.0 final stretch > > There should be a sample of each in the swig directory tree somewhere. I > can check in an hour our so, when I get home. > > - Greg > On Jul 7, 2013 11:42 AM, "Troy A. Griffitts" <scr...@crosswire.org> > wrote: >> >> OK guys, >> >> I have just updated the autotools stuff and the README files to build the >> swig bindings for both Perl and Python. Anyone know how to use SWORD with >> Perl or Python and can let me know if it actually works? >> >> Troy >> >> >> >> On 07/06/2013 03:04 PM, Peter von Kaehne wrote: >> >> On Sat, 2013-07-06 at 04:00 +0200, Troy A. Griffitts wrote: >> >> Peter, still wondering if we have a problem we need to fix for you. Do >> our Perl and Python bindings work for other people with a similar >> configuration as you? >> >> I have not heard from anyone that the Perl bindings are working nor have >> I heard from anyone with any clever ideas why they are not working. >> >> From a module making point of view the bindings are a must. But I do not >> care if they are working in in 1.7 or in a subsequent iteration as long >> as it is soon enough again. >> >> Peter >> >> >> >> _______________________________________________ >> sword-devel mailing list: >> sword-devel@crosswire.orghttp://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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 >
_______________________________________________ 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