From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Tue, 26 Feb 2013 08:17:41 +0100
Subject: [U-Boot] [PATCH 1/4] common: imx: Implement generic u-boot.nand
	target
In-Reply-To: <1361833645.27903.15@snotra>
References: <1361823013.27903.8@snotra> <201302260003.30640.marex@denx.de>
	<1361833645.27903.15@snotra>
Message-ID: <201302260817.41960.marex@denx.de>
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

Dear Scott Wood,

> On 02/25/2013 05:03:30 PM, Marek Vasut wrote:
> > Dear Scott Wood,
> > 
> > > So maybe we need a more general (but optional) CONFIG_BUILD_TARGET.
> > 
> > Can you elaborate?
> 
> Same as CONFIG_SPL_TARGET, but not SPL-specific.  Basically a way for a
> board config file to add to $(ALL-y).
> 
> > > So each one would set the appropriate CONFIG_BUILD_TARGET for
> > 
> > whatever
> > 
> > > needs to get built, and then something like CONFIG_NAND_IMAGE could
> > > hold the image name that should be linked to produce a standard
> > > u-boot-nand.bin output.
> > 
> > Yea, sounds reasonable. But why call it CONFIG_ , it can't be stored
> > in the
> > board.h files, it has to be somewhere in the Makefile hierarchy.
> 
> Why can't it go in the board.h files?

How would a config file contain the CPU-specific portions of a Makefile?

> -Scott

Best regards,
Marek Vasut