From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: "Dirk Süsserott" <newsletter@dirk.my1.cc>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: msysGit and SCons: broken?
Date: Thu, 13 Aug 2009 21:32:42 +0200 [thread overview]
Message-ID: <4A846A5A.4000000@dirk.my1.cc> (raw)
In-Reply-To: <4A7B32EA.2080505@dirk.my1.cc>
Am 06.08.2009 21:45 schrieb Dirk Süsserott:
> Am 04.08.2009 00:13 schrieb Johannes Schindelin:
>> On Mon, 3 Aug 2009, Dirk Süsserott wrote:
>>
>> How does your SCons call relate to Git? Do you call it from the Git
>> Bash? Do you call it from cmd.exe directly? Is Git/bash in your PATH?
>
> I used to call SCons from Git-bash and it worked. After Git's upgrade
> (or some other unknown change) I did the same and it didn't work from
> Git-bash, but it still worked from cmd.exe. Git-bash ist not in my PATH
> when I run cmd.exe.
If someone had the same or a similar problem: I tracked it down and
found a solution. The problem was that I tried to run a Windows program
from git-bash. The Windows program then faces the bash's $PATH with a
different separator (':' vs. ';') and a different root directory ('/c/'
vs. 'C:/'). Scons tries to split the PATH apart to figure out which
tools are installed. ActivePython thinks ';' is the right separator and
then fails. Thus, I wrote a wrapper to call Scons after manipulating the
$PATH variable by first exchanging the separator and then exchanging
'/c/' with 'c:/'.
Funny, though, that my things worked a few weeks ago *without* this
wrapper. Dunno why. At least it hasn't anything to do with my Git
update. I proved that by installing earlier versions of Git.
Dirk
next prev parent reply other threads:[~2009-08-13 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 18:19 msysGit and SCons: broken? Dirk Süsserott
2009-08-03 22:13 ` Johannes Schindelin
2009-08-06 19:45 ` Dirk Süsserott
2009-08-13 19:32 ` Dirk Süsserott [this message]
2009-08-13 21:54 ` Johannes Schindelin
2009-08-15 14:04 ` Dirk Süsserott
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=4A846A5A.4000000@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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).