From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Johannes Sixt <j.sixt@viscovery.net>,
msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [PATCH] mingw: disable Python
Date: Fri, 8 Jan 2010 14:55:49 +0100 [thread overview]
Message-ID: <40aa078e1001080555w1656032dr7d5cc3ca52fffe7f@mail.gmail.com> (raw)
In-Reply-To: <7vpr5kpvmh.fsf@alter.siamese.dyndns.org>
On Fri, Jan 8, 2010 at 2:35 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Erik Faye-Lund <kusmabite@googlemail.com> writes:
>
>>> On Fri, 8 Jan 2010, Johannes Sixt wrote:
>>>
>>>> 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?);
>>
>>> How about
>>>
>>> NO_PYTHON=
>>>
>>> in config.mak?
>>
>> That doesn't work for me, at least not out of the box. NO_PYTHON is
>> still defined, it's just defined to an empty string.
>
> I think Dscho is right. "ifdef FOO" yields (and should yield) false if
> FOO is set to empty.
>
In that case I guess I messed up my test. I'll retest.
Yes, I messed up. "NO_PYTHON=" works like a charm.
So, no repost :)
--
Erik "kusma" Faye-Lund
prev parent reply other threads:[~2010-01-08 13:55 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
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 [this message]
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=40aa078e1001080555w1656032dr7d5cc3ca52fffe7f@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=kusmabite@gmail.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).