From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Wed, 30 Jul 2014 17:05:21 -0600
Subject: [U-Boot] [PATCH v8 05/13] kconfig: switch to Kconfig
In-Reply-To: <1406696905-25756-6-git-send-email-yamada.m@jp.panasonic.com>
References: <1406696905-25756-1-git-send-email-yamada.m@jp.panasonic.com>
	<1406696905-25756-6-git-send-email-yamada.m@jp.panasonic.com>
Message-ID: <53D97A31.30805@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 07/29/2014 11:08 PM, Masahiro Yamada wrote:
> This commit enables Kconfig.
> Going forward, we use Kconfig for the board configuration.
> mkconfig will never be used. Nor will include/config.mk be generated.
>
> Kconfig must be adjusted for U-Boot because our situation is
> a little more complicated than Linux Kernel.
> We have to generate multiple boot images (Normal, SPL, TPL)
> from one source tree.
> Each image needs its own configuration input.
>
> Usage:
>
> Run "make <board>_defconfig" to do the board configuration.

This is quite unfortunate; it breaks any scripts that were building 
U-Boot via "make <board>_config; make". Can't we add another rule to 
allow the old build commands to work?

Otherwise, I guess I'll have to hack my scripts to check whether e.g. 
scripts/multiconfig.py (which was added in this commit) is present in 
the tree, and execute different build commands based on that...