On Thu, Oct 20, 2011 at 3:25 AM, Carmelo AMOROSO <[email protected]> wrote: > On 25/08/2011 17.58, Khem Raj wrote: >> On Wed, Aug 24, 2011 at 8:54 AM, Carmelo AMOROSO <[email protected]> >> wrote: >>> On 24/08/2011 17.50, Khem Raj wrote: >>>> On 8/24/2011 7:19 AM, Carmelo AMOROSO wrote: >>>>> Add a new option CONFIG to specify different defconfigs for each ARCH. >>>>> The naming convention assume that the defconfig are defined as >>>>> $(ARCH)_$(CONFIG) >>>>> >>>>> i.e. >>>>> make ARCH=sh CONFIG=prelink defconfig >>>>> >>>>> will look for extra/Configs/defconfigs/sh_prelink >>>> >>>> while not opposed to this patch I think this fragmentation can lead to >>>> usage complexity something like what linux kernel does could be an option >>>> >>> >>> Hi Khem, >>> sorry but I've not understood what you mean, regarding the "option". >>> >>> If it can help, CONFIG is not mandatory. >>> It is still possible to use simply make ARCH=<arch> defconfig. >> >> yes I understand that but I meant something like where kernel has >> machine configs in config dir >> may be >> > > Hi Khem > now I've understood... sorry. > You mean something like > > %_defconfig: $(top_builddir)extra/config/conf > $(Q)$(top_builddir)extra/config/conf \ > -D extra/Configs/defconfigs/$@ extra/Configs/Config.in > > correct ?
Yep _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
