From: Johannes Sixt <j.sixt@viscovery.net>
To: Erik Faye-Lund <kusmabite@googlemail.com>
Cc: msysgit@googlegroups.com, git@vger.kernel.org,
Erik Faye-Lund <kusmabite@gmail.com>
Subject: Re: [PATCH] mingw: disable Python
Date: Fri, 08 Jan 2010 09:07:50 +0100 [thread overview]
Message-ID: <4B46E7D6.3080702@viscovery.net> (raw)
In-Reply-To: <1262902037-4420-1-git-send-email-kusmabite@gmail.com>
Erik Faye-Lund schrieb:
> Python is not commonly installed on Windows machines, so
> we should disable it there by default.
>
> --- a/Makefile
> +++ b/Makefile
> @@ -1027,6 +1027,7 @@ ifneq (,$(findstring MINGW,$(uname_S)))
> + NO_PYTHON = YesPlease
I'm worried that with this solution it is impossible to re-enable Python
in config.mak (how do you undefine a Makefile variable?); it would be
necessary to hack Makefile.
Wouldn't it be superior to set
PYTHON_PATH =
in the MinGW section[*]. It works because there is this heuristic later:
ifeq ($(PYTHON_PATH),)
NO_PYTHON=NoThanks
endif
To enable Python, the user would have to set PYTHON_PATH in config.mak.
[I have only Python 1.6 to test (doh!), so I can only tell that it gets
used during 'make', but this fails due to missing modules, so I cannot
tell whether there would be a usable result if Python were sufficiently
recent.]
[*] You should probably set the MSVC section as well, even if you cannot
test it. The effect of the change is predictable enough, I think.
-- Hannes
next prev parent reply other threads:[~2010-01-08 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 21:52 [PATCH] mingw: enable NO_PYTHON Erik Faye-Lund
2010-01-07 22:00 ` Erik Faye-Lund
2010-01-07 22:07 ` [PATCH] mingw: disable Python Erik Faye-Lund
2010-01-08 8:07 ` Johannes Sixt [this message]
2010-01-08 10:35 ` Johannes Schindelin
2010-01-08 10:49 ` Erik Faye-Lund
2010-01-08 13:35 ` Junio C Hamano
2010-01-08 13:52 ` Johannes Sixt
2010-01-08 13:55 ` Erik Faye-Lund
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=4B46E7D6.3080702@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=kusmabite@googlemail.com \
--cc=msysgit@googlegroups.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 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).