Quoting Johannes Schindelin <[EMAIL PROTECTED]>:
> 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.
Ok, will do so.
Then you can test git-svn by
$ cd /git/t
$ sh t9100* -i -v
Sounds good.
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.
Python was needed when calling ./autogen.sh, or at least the script
claimed it were necessary. That's why I thought it is necessary. Swig
is necessary to create the wrapper c files by oneself, but now that
you say it, the subversion tarball probably contains all required
files already. At least that's the whole point of a tarball.
* You nee a shared library version of libz, e.g. zlib1.dll.
I installed from scratch (see /src/zlib/release.sh)... but I did not
check if it was built as shared lib or not.
I'll check later, but according to the fileList.txt only a libz.a
(i.e. static one) was built, which isn't enough.
* (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.
Okay.
Thanks,
Christian
