On Wednesday 18 December 2019 at 09:19:20 +0800, ChenQi wrote:
> On 12/17/2019 09:55 PM, Mike Crowe wrote:
> > On Tuesday 17 December 2019 at 16:56:11 +0800, ChenQi wrote:
> > > On 12/17/2019 04:02 PM, Mike Crowe via Openembedded-core wrote:
> > > > Ensure that
On Tuesday 17 December 2019 at 16:56:11 +0800, ChenQi wrote:
> On 12/17/2019 04:02 PM, Mike Crowe via Openembedded-core wrote:
> > Ensure that RECIPE_SYSROOT is the same for -native recipes whether
> > multilib.conf is included or not.
> >
> > Without this change
Ensure that RECIPE_SYSROOT is the same for -native recipes whether
multilib.conf is included or not.
Without this change task signatures for -native recipes change when
switching between MACHINEs that require multilib.conf and those that
don't.
This fix was one of the ones suggested by Khem Raj i
On Thursday 12 December 2019 at 18:17:37 +, Richard Purdie wrote:
> On Thu, 2019-12-12 at 16:05 +0000, Mike Crowe via Openembedded-core
> wrote:
> > We compile for a variety of machines, some of which require
> > multilib.conf
> > and some that do not. I was su
We compile for a variety of machines, some of which require multilib.conf
and some that do not. I was surprised to discover when switching between
machines that the do_populate_sysroot_setscene tasks run for many -native
recipe. :(
It looks like this is because RECIPE_SYSROOT changes:
Variable R
I'd like to use a single set of device tree sources for both the kernel and
U-Boot. I'd like to take the dtb files generated when compiling the kernel
and use it for U-Boot. This means that I need to able to find them from the
U-Boot recipe - ideally without having a list of them there.
So, I thou
kernel.bbclass installs non-standard kernels (where
KERNEL_PACKAGE_NAME is not "kernel") in a subdirectory of ${DEPLOYDIR}.
To achieve this kernel_do_deploy sets the deployDir shell variable to
${DEPLOYDIR} for the standard kernel or
${DEPLOYDIR}/${KERNEL_DEPLOYSUBDIR} for non-standard kernels.
ke
kernel.bbclass installs non-standard kernels (where
KERNEL_PACKAGE_NAME is not "kernel") in a subdirectory of ${DEPLOYDIR}.
To achieve this kernel_do_deploy sets the deployDir shell variable to
${DEPLOYDIR} for the standard kernel or
${DEPLOYDIR}/${KERNEL_DEPLOYSUBDIR} for non-standard kernels.
ke
