Hi,

On Jan 14, 12:40 pm, Johannes Schindelin <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> On Mon, 14 Jan 2008, Juanma Barranquero wrote:
> > On Jan 14, 2008 4:51 PM, Johannes Schindelin <[EMAIL PROTECTED]> wrote:
>
> > > Windows experience is, and how to compile Perl modules for Windows.
>
> > Not much experience compiling Perl modules (outside of "perl
> > Makefile.PL; make; make test; make install"), but I have experience as a
> > C and Perl programmer on Windows. I can try. Where to start from?
>
> First, get a full clone of msysgit.git (or update it if you have a partial
> one).
>
> I uploaded an intermediate state (not to be integrated as-is) to tmp/msys.
> But beware: you have to start msys.bat again after checking out tmp/msys,
> otherwise you will still be in a MinGW system, not an MSys one.
>
> After that, you can go to /src/perl and fetch&make&install perl 5.8.8 (For
> some strange reason, perl < 5.8 is not good enough for subversion).
>
> The next steps are to fetch&make&install expat, get subversion and
> subversion-deps, adjust subversion so it compiles with MSys (not MinGW),
> then make it, make "swig-pl-lib", "install-swig-pl-lib", and then the fun
> starts:
>
> In subversion/bindings/swig/perl/native, run "perl Makefile.PL".  Find out
> why it creates the Makefiles in ../libswig_perl_lib/.libs/, or move them
> to the correct directory, and adjust them, because libsvn_* was not built
> shared, but static.

Using subversion-1.4.x on linux, I've installed working svn perl
bindings many times with "make swig-pl && make install-swig-pl". No
extra steps should be required. I.e., you shouldn't have to run "perl
Makefile.PL" because the make target does that for you.

However, I do happen to know that the build is broken in that it
relies on macros defined by `perl -V:cflags' to set what is needed by
`apr-1-config --cppflags'.

If you can show more of an error, I might be able to suggest a fix. I
don't really have a Windows development machine, but I might be able
to figure something out and take a look.

--
Dan

Reply via email to