Hi,

On Tue, 22 Jan 2008, Christian Stimming wrote:

> Hi Johannes,
> 
> Quoting Johannes Schindelin <[EMAIL PROTECTED]>:
> > > [...] git-svn doesn't yet work on Msys mostly because the perl bindings
> > 
> > That's not really the problem... I got them to build by now.
> 
> You did? Anywhere in msysgit.git?

As I said, the script /src/subversion/release.sh is the (preliminary) 
result of my work.

> > > As for your question in that message why the libsvn_* are not built 
> > > dynamically:
> > 
> > I am not 100% convinced that this is the issue.  I would be very happy 
> > if it was, as you seem to be able to fix it.
> 
> I was able to fix this, description below. However, I also don't know 
> whether this helps anything.

Let's see, then, if it helps ;-)

> > I would be so delighted if you could check out the "temp/msys/" branch 
> > of msysgit.git and try your luck...
> 
> I already have a clone of msysgit.git, cloned with a git from the binary 
> installer. However, the /git directory is empty and I don't understand 
> how I can download or clone or install a git in the msysgit.git 
> environment.

Ah.  The recommended way to contribute to git is by installing via the 
netinstaller; this sets the complete environment up, compiles git and 
installs it.

In your case, nothing's lost, however.  You should be able to get /git 
(and for that matter, /doc/git/html) by

        $ cd /
        $ git submodule init
        $ git submodule update

But this is not strictly needed if you just want to build subversion.  To 
do that, a simple

        $ /src/subversion/release.sh

should be enough.

But if you want to test git-svn, you need to build git, of course:

        $ cd /git
        $ make

Then you can test git-svn by

        $ cd /git/t
        $ sh t9100* -i -v

> > if you succeed to patch "configure" and the "Makefile.in"s, please 
> > just commit the changes, and export them to /src/subversion/patches/ 
> > as a new patch.
> 
> As I still haven't understood your current working modus in msysgit, I 
> just attached my patches to this email.

Thanks, I'll try to integrate them...

> > P.S.: Isn't it strange? It seems like all the serious contributors 
> > (those who don't go away after a few mails) are from central Europe...
> 
> :-) PS: Your email sending times are "strange", too...

Oh yes ;-)

> Description of how I got a shared library build of subversion-1.4.6:
> 
> * Prerequisites: Have python and swig (any recent should be fine) installed
> somewhere. Have python.exe and swig.exe in your PATH.

Are those really necessary?  I tried without, and it compiled.  Also, 
python and swig should not have any impact on subversion-perl being built 
shared, or crashing.

> * You nee a shared library version of libz, e.g. zlib1.dll. In gnucash we
> created the import libray .dll.a ourselves as follows:
>  - Download a zlib1 package,
> ftp.gtk.org/pub/gtk/v2.10/win32/dependencies/zlib123-dll.zip ;
>  - unpack it into /usr;
>  - cd /usr; mv zlib1.dll /usr/bin
>  - cd /usr/bin; dlltool.exe -D zlib1.dll -d ../lib/zlib.def -l libz.dll.a; mv
> libz.dll.a ../lib

I installed from scratch (see /src/zlib/release.sh)...  but I did not 
check if it was built as shared lib or not.

> * Unpack subversion and subversion-deps
> 
> * Apply patches from src/subversion/patches plus the attached three more
> patches (sorry, only diff -ur format)

That format is just fine for me.

> * (probably) install the latest libtool, e.g. 1.5.22, into the msysgit.git
> environment - maybe this isn't necessary, though.

I'll try without, and if it does not work, we'll know.

> * cd /src/subversion/subversion-1.4.6;  and now the fun starts:
>  ./autogen.sh  # to rebuild the build system
> 
>  ./configure --disable-static --enable-shared --build=i686-pc-mingw32
> 
>  make LDFLAGS="-no-undefined -Wl,-enable-auto-import -L/lib"
> 
> (this will eventually fail somewhere in tests but I ignored that)
> 
>  make swig-pl-lib LDFLAGS="-no-undefined -Wl,-enable-auto-import -L/lib"
> LIBS="-L/lib/perl5/5.8.8/msys/CORE -lperl"
> 
> This gives dlls of everything, including
> bindings/swig/perl/libsvn_swig_perl/.libs/libsvn_swig_perl-1-0.dll

I will incorporate your patches, and the recipe to use configure.  Will 
keep you posted!

Thanks,
Dscho

Reply via email to