Re: Linkage of SWIG/PYthon bindings against libpython on Solaris with gcc
On Wed, 21 Dec 2005, Daniel Rall wrote:
> On Wed, 21 Dec 2005, Max Bowsher wrote:
> > Daniel Rall wrote:
> > > What's the need behind the explicit linkage with of the bindings with
> > > libpython?
> > It's absolutely required on PE targets (i.e. Cygwin).
> > It's not at all required on Linux ELF.
> > It may or may not be important on Darwin.
> > It likely isn't required on at least some miscellaneous Unixes.
> > > Understandably, I would prefer to be able to build Subversion's
> > > bindings against Python 2.2.3, rather than upgrade Python. Thoughts?
> > Since Python doesn't appear to be handing us linker arguments which can
> > be unconditionally used as is, just give up and conditionalize
> > get-py-info.py --libs to only return anything on Cygwin and Darwin.
> Max, I began implementing this, then started wondering if it wouldn't
> be more appropriate to have swig.m4 not call 'get-py-info.py --libs'
> under Cygwin and Darwin (rather than changing get-py-info.py itself).
Scratch that -- your suggested implementation is spot on. Added to
trunk in r17910, and proposed for backport to 1.3.1.
Received on Sun Dec 25 02:36:07 2005
- application/pgp-signature attachment: stored
This is an archived mail posted to the Subversion Dev