On Tue, Nov 08, 2005 at 10:29:46PM +0100, Joachim Ansorg wrote: > There's a SWIG binding to Sword in the source code package. > I don't know if Python is working as it should with it, tough.
Nifty. Unfortunately, I'm not able to get them to compile. It goes past the perl bindings with no problem. I'm using debian, w/ libsword and libsword-dev installed. the output from make: mkdir -p python echo "writing python/setup.py" writing python/setup.py cd python && /usr/bin/python setup.py build_ext -I/usr/include/sword -L/usr/lib -lsword running build_ext building '_Sword' extension creating build creating build/temp.linux-i686-2.3 gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -DSWIG=1 -I/usr/include/sword -I/usr/include/python2.3 -c Sword.cxx -o build/temp.linux-i686-2.3/Sword.o gcc: Sword.cxx: No such file or directory gcc: No input files error: command 'gcc' failed with exit status 1 make: *** [python_make] Error 1 anyone have any suggestions? thanks --B _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
