Russell Yanofsky wrote:
> Max Bowsher wrote:
>> Russell Yanofsky wrote:
>>> Max Bowsher wrote:
>>>> r10233 was a change to the perl bindings. However, some of it
>>>> affected the build of all swig bindings. The python bindings are
>>>> now broken, because of a circular dependency between
>>>> libsvn_swig_py and swig_core.
>>>> One solution would be to build the swig runtime code into
>>>> libsvn_swig_*, not into swig_core.
>>> r10236 should fix this problem. It does keep the runtime in
>>> swig_core though.
>> That's good enough for unix, but Cygwin's still broken.
>> Could you give a short summary of the reason for these re-designs, so
>> I can be sure not to work against your goals as I try to fix the
>> bindings on Cygwin?
> The only changes that affect the unix builds are r10233 and r10236.
> The goal of these changes was just to include the swig runtime
> functions in the core swig modules (_core.so, _core.dll) so we don't
> have to depend on external swig runtime libaries (-lswigpy). This is
> implemented by passing
> the -runtime parameter when we invoke swig to generate the core
> module. r10233 implemented this on windows and r10236 implemented it
> on unix. Probably the reason these changes don't work on cygwin is
> that there is now a mutual dependency between the libsvn_swig_python
> library and the core module. The core module has always depended on
> libsvn_swig_python, but the libsvn_swig_python library only now
> depends on the core module so it can access the swig runtime.
> Probably the easiest way to fix this problem is to compile
> libsvn_swig_python as a static library like we talked about on irc.
> I'd appreciate any help you can offer with this since you know more
> about libtool than I do. I'll probably have some time tommorrow to
> work on it myself.
I think the attached patch should fix this, although I haven't tested it
myself because I can't get subversion to build on cygwin.
Received on Wed Jul 14 02:52:14 2004
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org