Re: [PATCH 3/4 v2] buildchroot: Add prepare and cleanup tasks

[Christian Storm <christian.storm@siemens.com>]

> Sorry, but I still don't understand how this patch brakes your build 
> because it doesn't influence on dependencies at all. 
> If you need strict order for packages to be built, then anyway you
> have to specify this in recipe:
> 
> In recipe B:
> 
> DEPENDS += "A"
> do_build[deptask] = "do_build"
> 
> It would be very helpful for me if you could provide recipes and workaround.


OK, here's one example, anonymized, that used to work:

```meta-mylayer/recipes-core/A/A.bb
...
SRC_URI = "git://..."
SRC_DIR = "git"

PROVIDES = "${PN}-dev"
inherit dpkg

dpkg_runbuild() {
  ...
  sudo chroot ${BUILDCHROOT_DIR} /build.sh ${PP}/${SRC_DIR}
  ...
}
```

This is a pretty standard recipe whose only purpose is to build two .deb
packages, one containing the binaries, one containing build-time
dependencies for B.bb below:
The resulting A-dev.deb package then contains, e.g., 
  /usr/lib/x86_64-linux-gnu/libA.a
and this is used as build-time dependency from B. Consider 
  /usr/lib/x86_64-linux-gnu/libA.a
to be linked into the software binary compiled by B.B.

```meta-mylayer/recipes-core/B/B.bb
...
SRC_URI = "git://..."
SRC_DIR = "git"

DEPENDS = "A-dev"
inherit dpkg

dpkg_runbuild() {
  ...
  ## UGLY hack to install build-time dependency A-dev required for the 
  ## software to be compiled here
  for item in $(echo ${DEPENDS} | sed 's/buildchroot//g'); do
    sudo dpkg --root=${BUILDCHROOT_DIR} -i ${DEPLOY_DIR_DEB}/${item}_*
  done

  sudo chroot ${BUILDCHROOT_DIR} /build.sh ${PP}/${SRC_DIR}
  ...
}
```

This does not work on current -next. Even if you do the 
  do_build[deptask] = "do_build"
because do_cleanup() kicks in and unmounts ${BUILDCHROOT_DIR}/git
and the task reordering of deploy_deb().


Hope this example helps?



   Christian

-- 
Dr. Christian Storm
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Otto-Hahn-Ring 6, 81739 M�nchen, Germany