On Thu, 2018-02-01 at 22:37 +0300, Alexander Smirnov wrote:
> 
> On 02/01/2018 09:37 PM, Claudius Heine wrote:
> > Hi,
> > 
> > On Thu, 2018-02-01 at 17:25 +0100, Jan Kiszka wrote:
> > > On 2018-02-01 17:22, Alexander Smirnov wrote:
> > > > On 02/01/2018 07:14 PM, Jan Kiszka wrote:
> > > > > On 2018-02-01 12:29, Alexander Smirnov wrote:
> > > > > > Hi all,
> > > > > > 
> > > > > > this series intended to make buildchroot able to work with
> > > > > > isar-apt.
> > > > > > I've tried to add extended comments to each patch.
> > > > > > 
> > > > > > Impact: with this series I'm able to build 'example-hello'
> > > > > > <->
> > > > > > 'libhello'
> > > > > > without any hacks. So the deps are installed automatically.
> > > > > > 
> > > > > > NOTE: I've migrated to bitbake [lockfiles] mechanism, don't
> > > > > > know how
> > > > > > robust it
> > > > > > is, but build in the loop started in the evening didn't
> > > > > > fail
> > > > > > during
> > > > > > the night.
> > > > > > 
> > > > > 
> > > > > I can happily report: It works as promised also for my use
> > > > > case
> > > > > (jailhouse.bb -> linux-jailhouse.bb, both Isar-built).
> > > > > 
> > > > 
> > > > Thanks! But I've found an issue with events. :-( Our bitbake
> > > > didn't
> > > > handle them for multiconfig, the following patch seems to add
> > > > this:
> > > > 
> > > > https://patchwork.openembedded.org/patch/141626/
> > > > 
> > > > Events is very good mechanism to clean up Isar build from
> > > > pending
> > > > mounts
> > > > without headache with build fails, so I think it would be
> > > > valuable
> > > > to
> > > > try latest bitbake. I'll report the results as soon as build
> > > > finishes.
> > > 
> > > Perfect: Claudius just told me we need to update bitbake anyway
> > > to
> > > have
> > > proper multiconfig support (i.e. no more hacky copying of files
> > > during
> > > isar-init-build-env). Claudius, which version at least?
> > 
> > I haven't tested it but I think its this one:
> > 
> > http://git.openembedded.org/bitbake/commit/?id=518b9015c2be8d389427
> > 7a8e
> > 54890d6f04d656c0
> > 
> 
> The following patch is needed for latest bitbake (derived from
> Yocto):
> 
> diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-
> bitbake.conf
> index 10cd45d..b853c88 100644
> --- a/meta/conf/isar-bitbake.conf
> +++ b/meta/conf/isar-bitbake.conf
> @@ -28,5 +28,6 @@ BUILDCHROOT_DIR = 
> "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot/rootfs"
>   BB_SIGNATURE_HANDLER ?= "noop"
> 
>   include conf/local.conf
> +include conf/multiconfig/${BB_CURRENT_MC}.conf
>   include conf/machine/${MACHINE}.conf
>   include conf/distro/${DISTRO}.conf

Right and that is exactly what is needed to be able to have own
multiconfigs in separate layers.

From the dates I suppose that your new bitbake version will contain
this commit, so then we could remove ISARMULTICONF stuff from isar-
init-build-env since copying is no longer needed.

Cheers,
Claudius



-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net