Isar build tree structure

[Alexander Smirnov <asmirnov@ilbers.de>]

Hi all,

I'd like to discuss build folders tree to somehow chose more suitable 
approach.

1. How it's done at the moment.

The folder tree contains the following main paths:

  - tmp/work/${PP}

It's a $WORKDIR for each recipe, here is stored bibtbake logs and 
commands, and data for packages that doesn't require buildchroot (for 
example, buildchroot and isar-image-base).

  - tmp/work/buildchroot/${DISTRO}-${ARCH}/rootfs/home/build/${PN}

This is the $BUILDROOT for packages, that require compilation in chroot. 
It is used as destination folder for unpack task.

Benefits:

  - Maximal common OE-like folder structure for all kind of recipes. You 
can find the information about specific package in 'tmp/work/${PP}'. And 
it doesn't matter if this package uses dpkg class, or not.

  - After buildchroot cleanup, the build information is not loosed.

  - For multiple buildchroots in project, there will be single place for 
package meta information.

2. Remove $BUILDROOT.

This would mean that $WORKDIR location may vary depending on recipe 
type. So the recipes data will be distributed across buildchroots and 
tmp/work dir.

Benefits:

  - Each recipe will use single folder for everything.



So... Ideas and opinions? :-)

-- 
With best regards,
Alexander Smirnov

ilbers GmbH
Baierbrunner Str. 28c
D-81379 Munich
+49 (89) 122 67 24-0
http://ilbers.de/
Commercial register Munich, HRB 214197
General manager: Baurzhan Ismagulov