From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cantor2.suse.de ([195.135.220.15]:48147 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755254Ab1EPUda (ORCPT ); Mon, 16 May 2011 16:33:30 -0400 Message-ID: <4DD18A18.5050006@suse.cz> Date: Mon, 16 May 2011 22:33:28 +0200 From: Michal Marek MIME-Version: 1.0 Subject: Re: [PATCH v2] kconfig: autogenerated config_is_xxx macro References: <1304658229-30820-1-git-send-email-plagnioj@jcrosoft.com> <20110507015041.GA21017@game.jcrosoft.org> <4DC7AB57.9050002@suse.cz> <20110513080909.GO18952@game.jcrosoft.org> <32557.1305572616@localhost> <4DD1838D.7030305@suse.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Arnaud Lacombe Cc: Valdis.Kletnieks@vt.edu, Jean-Christophe PLAGNIOL-VILLARD , linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, x86@kernel.org, Ingo Molnar On 16.5.2011 22:24, Arnaud Lacombe wrote: > Hi, > > On Mon, May 16, 2011 at 4:05 PM, Michal Marek wrote: >> I figure that this feature is not wanted outside of the kernel build, >> though. So what about an option to 'conf' that controls whether these >> macros will be generated? >> > kconfig internal behaviors are mostly controlled by environment > variable, which has the advantage to be front-end agnostic, that might > be better. Note that the header file is written by scripts/kconfig/conf --silentoldconfig, so different front-ends are not an issue. But an environment variable works fine as well. Michal