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

Re: svn commit: r10039 - in trunk: . build/generator subversion/bindings/swig subversion/bindings/swig/perl/libsvn_swig_perl subversion/bindings/swig/perl/native

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-06-21 11:38:37 CEST

Ben Reser wrote:

>On Mon, Jun 21, 2004 at 01:10:25AM +0200, Branko ??ibej wrote:
>
>
>>This is exactly the kind of exceptions we don't need. Is there really no
>>way to handle the perl SWIG bindings the same way as any other SWIG
>>bindings? At the very least, this should be handled with a _property_ of
>>the section in build.conf, the generator shouldn't depend on the section
>>name.
>>
>>
>
>The perl bindings are not in build.conf anymore, with the exception of
>the swig-pl-lib target. We're using the infrastructure that Perl
>provides for building and installing extensions. In order to just use
>the generator we'd have to re-engineer all of this infrastructure. I'm
>not inclined to do that...
>
So right now we have the worst possible situation, with Unix and Windows
doing completely different things with the Perl bindings. Hm.

I see Unix uses the Perl infrastructure (Makfile.PL, and such) for
building and installing the bindings. I suggest Windows should do the
same, because Perl _does_ support building on Windws using the same
mechanism.

Can we work on making it so?

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 21 11:39:12 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.