git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Thoyts <patthoyts@googlemail.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>,
	msysGit Mailinglist <msysgit@googlegroups.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [msysGit] [PATCH 2/3] git-gui: fix PATH environment for mingw  development environment
Date: Sun, 28 Feb 2010 00:57:14 +0000	[thread overview]
Message-ID: <a5b261831002271657n41ab0f37sc0af50d3a768bfd1@mail.gmail.com> (raw)
In-Reply-To: <20100227204741.GC33000@book.hvoigt.net>

On 27 February 2010 20:47, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> When creating a desktop shortcut from the gui the shortcut directly
> starts wish with the git-gui script. In the msysgit development
> environment some dll's reside in the mingw/bin directory which causes
> that git can not start because libiconv2.dll is not found.
>
> When using such a link the error is even more cryptic stating:
> "child killed: unknown signal"
>
> Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net>
> ---
> I am not sure whether this is the most elegant solution, but making this
> work would definitely ease the development workflow.
>
>  git-gui/windows/git-gui.sh |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/git-gui/windows/git-gui.sh b/git-gui/windows/git-gui.sh
> index 66bbb2f..b1845c5 100644
> --- a/git-gui/windows/git-gui.sh
> +++ b/git-gui/windows/git-gui.sh
> @@ -13,10 +13,11 @@ if { $argc >=2 && [lindex $argv 0] == "--working-dir" } {
>        incr argc -2
>  }
>
> -set bindir [file dirname \
> +set basedir [file dirname \
>             [file dirname \
>              [file dirname [info script]]]]
> -set bindir [file join $bindir bin]
> +set bindir [file join $basedir bin]
> +set bindir "$bindir;[file join $basedir mingw bin]"
>  regsub -all ";" $bindir "\\;" bindir
>  set env(PATH) "$bindir;$env(PATH)"
>  unset bindir
> --
> 1.7.0.m5.rc3.5.g38df2

I have not tried to test this - I use cmd shell all the time so I
always run this using 'git gui' which runs the git.cmd script in
ProgramFiles\Git\cmd or in the development environment in
msysgit\cmd\. It makes me wonder if the Windows shortcut shouldn;t be
pointing to the cmd script rather than to a tcl script like this as
the cmd script does some quite extensive environment setup. It assigns
HOME if it is not set, extends the PATH to include the git
installation locations, sets the PLINK_PROTOCOL and the codepages for
the console. Probably only the PATH and HOME fixups are necessary for
git-gui and in fact tcl's configuration of "~" in the path as HOME
probably deals with that too.
This is just for the development setup right? An installation of
msysGit doesn't have a mingw\bin directory.
Pat Thoyts

  reply	other threads:[~2010-02-28  0:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23 22:49 git gui create desktop icon currently does not work Heiko Voigt
2010-02-23 22:54 ` Giuseppe Bilotta
2010-02-23 23:02   ` Heiko Voigt
2010-02-25  7:53     ` Giuseppe Bilotta
2010-02-27 20:41       ` Heiko Voigt
2010-02-27 20:45         ` [PATCH 1/3] git-gui: fix usage of _gitworktree when creating shortcut for windows Heiko Voigt
2010-02-27 20:47           ` [PATCH 2/3] git-gui: fix PATH environment for mingw development environment Heiko Voigt
2010-02-28  0:57             ` Pat Thoyts [this message]
2010-02-28 12:46               ` Heiko Voigt
2010-02-27 20:48           ` [PATCH 3/3] git-gui: fix shortcut creation on cygwin Heiko Voigt
2010-03-08 11:17           ` [PATCH 1/3] git-gui: fix usage of _gitworktree when creating shortcut for windows Johannes Schindelin
2010-02-27 22:09         ` Re: Re: git gui create desktop icon currently does not work Giuseppe Bilotta

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=a5b261831002271657n41ab0f37sc0af50d3a768bfd1@mail.gmail.com \
    --to=patthoyts@googlemail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=hvoigt@hvoigt.net \
    --cc=msysgit@googlegroups.com \
    --cc=spearce@spearce.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).