Hei hei, Am Dienstag, 16. Oktober 2018, 09:52:55 CEST schrieb Michael Olbrich: > On Wed, Oct 10, 2018 at 02:03:33PM +0200, Ahmad Fatoum wrote: > > while at it, remove U_BOOT_PATH, because it's PATH=$(CROSS_PATH) already > > by default. > > > > Signed-off-by: Ahmad Fatoum <a.fat...@pengutronix.de> > > --- > > > > rules/u-boot.make | 42 ++++++++++++++++++++++++++++++++++-------- > > 1 file changed, 34 insertions(+), 8 deletions(-) > > > > diff --git a/rules/u-boot.make b/rules/u-boot.make > > index aa7a01ca8fea..46cfc192825a 100644 > > --- a/rules/u-boot.make > > +++ b/rules/u-boot.make > > @@ -26,6 +26,9 @@ U_BOOT_SOURCE := $(SRCDIR)/$(U_BOOT).$(U_BOOT_SUFFIX) > > > > U_BOOT_DIR := $(BUILDDIR)/$(U_BOOT) > > U_BOOT_LICENSE := GPL-2.0-only > > > > +U_BOOT_CONFIG := $(call ptx/in-platformconfigdir, \ > > + $(call remove_quotes, $(PTXCONF_U_BOOT_CONFIG))) > > So, I'm pretty sure that the u-boot 'config' was simply a make target in > the past, not a config file. > Has this changed for all target or do we need an option to support both?
You may need both. U-Boot has started introducing KConfig some time ago and is in the (long) process of migrating all options to it. What you provide as make target to recent U-Boot versions is actually a KConfig defconfig which overwrites your .config and which is somehow magically merged with preprocessor defines in includes/configs/yourboardname.h until the migration process is done. (Correct me, if I understood that wrong.) What I currently do is on a u-boot clone apart from ptxdist: menuconfig, then savedefconfig, copy that over, commit in my u-boot tree, export patches and use it as a defconfig make target in ptxdist. Greets Alex _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de
