Yay! I finally got the Sword Python bindings for Windows built tonight.
Like Ben said, I just needed to define the macro SWUSINGDLL and it all
worked. Thanks to everyone (especially Greg Hellings and the Morgan
brothers) who helped me along the way.
I still have a long way to go, as now I
I also tried changing the command in step 3 (setup.py build) to use
libsword.lib rather than sword.lib by replacing the lines in the
setup.py file:
setup(name='sword',version='1.7.3',
libraries=[('sword')],
with:
setup(name='libsword',version='1.7.3',
I could be completely off base here but I believe that those lines are looking
for sword.dll, not sword.lib or libsword.lib.
On October 7, 2014 2:02:36 AM CEST, R Johnson
ps16thypresenceisfullnessof...@gmail.com wrote:
I also tried changing the command in step 3 (setup.py build) to use
I think those items are all the data definitions.
I've run into errors like that before. If you are buildings Sword itself as
a DLL, you need to define the macro SWUSINGDLL while compiling the C++
bindings code for it all to work. I forget exactly how you change setup.py
to make it do that,
Thanks for the suggestion, Nic. I don't think it would work to use
cygwin, because I have to use the same compiler that Python is built
with on Windows to be able to build the SWIG bindings, but maybe I
should look into building Sword without ICU.
I corresponded with Greg Hellings, and he
