On Mon, Jun 21, 2004 at 03:02:10PM -0400, Russell Yanofsky wrote:
> Branko ÄOibej wrote:
> > 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?
>
> That's a reasonable solution, although I don't like it because it would mean
> you could no longer build the bindings with Visual Studio and because it
> would make the perl bindings build differently than the other swig bindings.
I don't see why this is a problem. They're already built differently
than the other swig bindings on unix like operating systems. But not
only that we're talking about language bindings. The idea that they all
should be built exactly the same way in some cookie cutter way seems to
me to be flawed. The target languages are necessarily different.
On Mon, Jun 21, 2004 at 02:58:32PM -0400, Russell Yanofsky wrote:
> Ben Reser wrote:
> > The perl bindings are not in build.conf anymore, with the exception of
> > the swig-pl-lib target.
>
> The perl bindings are back in build.conf, I had to add them so they could
> build under windows.
Yeah and I'm not thrilled about this. We now have targets sitting in
the build-outputs.mk that are total useless and don't work anyway.
$ make subversion/bindings/swig/perl/_Client.la
mkdir subversion/bindings/swig/java/build
/home/breser/wc/svn-trunk/subversion/bindings/swig/svn_client.i
make: execvp:
/home/breser/wc/svn-trunk/subversion/bindings/swig/svn_client.i:
Permission denied
make: *** [subversion/bindings/swig/perl/svn_client.c] Error 127
(And why the heck is it making a java directory to build a perl 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...
>
> Couldn't you use the build generator to build the extensions and the
> existing Perl infrastructure to install them? The build generator already
> knows how to build swig modules, it just needs to be tweaked to use the
> right parameters and filenames.
The build generator only knows how to build the libsvn_swig_perl
library. As far as I know it has never known how to build the actual
bindings, not just our support library, properly.
I find it really odd that you advocated a build process that is
obviously completely different than the other swig bindings builds and
then 4 minutes later argue against the current setup on the basis that
it is different the other swig bindings build.
There's no reason we can't make the Makefile.PL work for Windows. Like
I pointed out before the symbols that need to be filled in to make a
Makefile.PL from Makefile.PL.in, you probably already have. I'm more
than willing to work with you to get Makefile.PL to work on Windows.
--
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 22 19:35:08 2004