Re: [PATCH 0/2] Set Makefile variables from configure
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Nov 4, 2009, 19:36 UTC
- Message-ID
- <7v7hu6gjzz.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <1257357960-12763-1-git-send-email-bwalton@artsci.utoronto.ca>
Ben Walton <bwalton@artsci.utoronto.ca> writes:
Show 14 quoted lines
> Ok, a second attempt, taking into account Jonathan's feedback and > proposed updates. The revised macro allows for specified help text. > > I opted to use a more 'dry' approach to the macro instead of repeating > the boilerplate AC_WITH_ARG bits when calling this feature. > > Additionally, I only WARN when 'yes' or 'no' is passed. Bailing on > errors in most cases is reasonable, but I don't think it's globally > appropriate. > > As to why I want this...It's cleaner, in my opinion, to do all build > configuration through a single mechanism than to do most with > ./configure and the rest with variables passed to make. In other > words, this is purely a style issue.
Sorry, I wasn't following the discussion primarily because I am totally uninterested in autoconf myself (it's purely a style issue and using a single mechanism of echoing into config.mak is just as clean), so allow me to ask a stupid question that might have been already answered while the initial round was discussed.
I am a bit puzzled about the "warning" logic. Is this because you expect variables we typically give YesPlease/NoThanks as their values will not be handled with this new PARSE_WITH_SET_MAKE_VAR() macro?