> -----Original Message----- > From: otavio.salva...@gmail.com [mailto:otavio.salva...@gmail.com] On > Behalf Of Otavio Salvador > Sent: Thursday, September 04, 2014 5:15 AM > > On Wed, Sep 3, 2014 at 5:42 AM, Zhenhua Luo <zhenhua....@freescale.com> > wrote: > > Signed-off-by: Zhenhua Luo <zhenhua....@freescale.com> > ... > > +# The ls1 defconfig is maintained in kernel source, copy it to # > > +${WORKDIR}/defconfig do_configure_prepend () { > > + if [ ! -f ${WORKDIR}/defconfig ] && [ -f ${KERNEL_DEFCONFIG} ]; > then > > + cp ${KERNEL_DEFCONFIG} ${WORKDIR}/defconfig > > + fi > > +} > > I understand why you does this however this makes very hard for users to > change the kernel config in a convenient way. Several users end doing > minor edits on the defconfig inside the layer for test purposes and I > think this is a good thing to have as we are very concerned with easy to > use. [Luo Zhenhua-B19537] I think above code is compatible with the defconfig usage in SRC_URI, defconfig defined in SRC_URI has the high priority. User can easily by add custom defconfig by append it in SRC_URI. BTW, menuconfig should be the better way to do kernel configure, isn't it?
> Can you use the defconfig in SRC_URI and put it in the layer? [Luo Zhenhua-B19537] FSL maintains the kernel defconfig in kernel source for all QorIQ targets, so we want Yocto to get defconfig from kernel source directly to ensure the recent defconfig will be built. Best Regards, Zhenhua -- _______________________________________________ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
