Re: [PATCH] work in progress perl typemaps for swig

On Tue, Jul 15, 2003 at 08:17:18AM -0400, Garrett Rooney wrote:
> Chia-liang Kao wrote:
>
> > note that I think it's better to build the perl bindings
> > with perl's standard way instead of libtool. libtool is

I very much disagree. We tried that with the Python bindings and using
distutil. We got screwed. Arguably, the Perl MakeMake thingy is better, but
I look at your sample Makefile.PL and still see a lot of problems. There are
a log of things that need to be passed into a proper build of SWIG
extensions. All kinds of paths, library names, version numbers, etc.

No... we should get the sucker integrated into the standard build system.
I'm torn on whether to include the Makefile.PL even temporarily. As long as
it is present, nobody will have any impetus to fix the real build system.

I'm guessing that you'll get a long ways just by doing some simple copy and
paste in the top-level Makefile.in for the swig-related symbols. Then adjust
the swig-languages option into build.conf and see what happens :-)

> > good for cross platform shared libraray building. but as
> > for perl (or maybe python too), on different platform there
> > might be different way to build their own shared object.
> > for example on Mac OS X, the libraries should be built as
> > .bundle instead of .dylib. and maybe this is why I can't
> > use python binding on Mac OS X: libtool links them as .so.
>
> That's a bug in libtool. Newer versions fix it. I know 1.5 does, and
> earlier versions might work, although I'm not sure which ones.

Right. And worst case, we can always apply some additional platform-specific
magic until we decide to move up to libtool 1.5 to fix the problems.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org