From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org, hanwen@xs4all.nl
Cc: "Marco Costalba" <mcostalba@gmail.com>
Subject: Re: Anyone running GIT on native Windows
Date: Fri, 11 May 2007 22:07:02 +0200 [thread overview]
Message-ID: <200705112207.02206.J.Sixt@eudaptics.com> (raw)
In-Reply-To: <f329bf540705111035v4a6f0b23w49f04c768a410069@mail.gmail.com>
On Friday 11 May 2007 19:35, Han-Wen Nienhuys wrote:
> 2007/5/11, Johannes Sixt <J.Sixt@eudaptics.com>:
> > Han-Wen Nienhuys wrote:
> > > http://lilypond.org/git/binaries/mingw/git-1.5.1-1.mingw.exe
> >
> > This resulted in a mostly working git toolset after I've done this in
> > addition to installing it:
> >
> > - Installed MSYS (of course ;)
> > - Install libiconv-2.dll, which can be found in
> > diffutils-2.8.7-1-dep.zip from
>
> Can you be more specific? Which files required this?
git.exe, for example, hence, at least all builtins.
> It is entirely coincidental that another DLL from another package
> works, and it's a bug in our packaging.
Why should this not work? The diffutils package I mentioned is from MinGW.
Anyway, I think we should not link against libiconv*.dll at all because it
slows down the startup too much.
> The path to Git should also have been set automatically. I will look into
> this.
Well, I did not reboot, or log out and in again. I just opened a CMD after the
installation was complete. Usually, CMD picks up new PATHs if they have been
modified via the Settings->System->Advanced (or whatsitcalled) tool. So, I
thought it would be the same with installations.
-- Hannes
next prev parent reply other threads:[~2007-05-11 20:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 6:50 Anyone running GIT on native Windows Aaron Gray
2007-05-06 7:19 ` Junio C Hamano
2007-05-06 7:39 ` Aaron Gray
2007-05-07 7:02 ` Johannes Sixt
2007-05-07 11:48 ` Marco Costalba
2007-05-07 12:01 ` Johannes Sixt
2007-05-07 12:38 ` A.S. Bradbury
2007-05-07 13:51 ` Aaron Gray
2007-05-07 14:24 ` Johannes Schindelin
2007-05-07 15:10 ` Thomas Glanzmann
2007-05-07 16:39 ` Aaron Gray
2007-05-07 17:45 ` Johannes Schindelin
2007-05-08 18:21 ` Asger Ottar Alstrup
2007-05-09 4:41 ` Han-Wen Nienhuys
2007-05-09 7:08 ` Johannes Sixt
2007-05-11 4:00 ` Han-Wen Nienhuys
2007-05-11 16:34 ` Johannes Sixt
2007-05-11 17:35 ` Han-Wen Nienhuys
2007-05-11 20:07 ` Johannes Sixt [this message]
2007-05-11 22:08 ` Han-Wen Nienhuys
2007-05-12 2:23 ` Aaron Gray
2007-05-09 18:31 ` Jan Hudec
2007-05-09 18:40 ` Han-Wen Nienhuys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200705112207.02206.J.Sixt@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
--cc=mcostalba@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.