[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: How to build the swig-python bindings on win32?

From: Patrick Mayweg <mayweg_at_qint.de>
Date: 2004-03-17 10:43:34 CET

Ben Reser wrote:

>On Wed, Mar 17, 2004 at 09:42:14AM +0100, Patrick Mayweg wrote:
>
>
>>I did that and it did not help. I am still getting the same link errors
>>and a new preprocessor warning. I had also to add PATH_TO_SWIG/lib to
>>the include path.
>>
>>Any more idea?
>>
>>
>
>Can you provide the full output of the build and exactly what you did?
>
>
>
Hi Ben,
I have found the reason for missing symbols during linking. On win32,
the subversion build also builds the swig runtime (swigpy.dll). To
generate the source file swigpy.c, the python script
build/win32/gen_swig_runtime.py is used. It is assembling swigpy.c from
some files in PATH_TO_SWIG/lib. There the file python/precommon.swg is
missing. After I have added python/precommon.swg to gen_swig_runtime.py
and rebuild all, at least the build completes.

The next question would be, what do we do with this information?
1. Put it into the INSTALL file. I would say that the instructions are
to complex for that.
2. Put it into gen-make.py (which generates the project files) I do not
know enough, how the projects files are generated.
3 ?

Patrick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 17 10:38:48 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.