[Toaster] YOCTO #9992

[Barros Pena, Belen]

On 10/08/2016 01:33, "toaster-bounces at yoctoproject.org on behalf of Brian
Avery" <toaster-bounces at yoctoproject.org on behalf of
avery.brian at gmail.com> wrote:

>I took a swing at fixing this today and I'd appreciate comments. My
>change kinda drastically alters the directory layout so we should see if
>we can agree on it and I certainly need to test it more.
>
>
>The branch is 
>http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=bavery/toast
>er/9992-builddir-not-build
>
>
>It does the following:
>1) changes the directory structure:
>   you end up with
>BUILDDIR from oe-init-build-env
>and TOASTER_DIR=$BUILDDIR/toaster
>all toaster files go into this directory.
>
>
>command line builds happen in BUILDDIR
>toaster project builds happen in BUILDDIR/toaster/build-toaster-<id>

I am not fully sure about this, mainly for 2 reasons:

1. Having the build directories for toaster projects inside the build
directory hides them from view, somehow making the Toaster behaviour
(spawning a build directory per project) less obvious.

2. By doing this, we have 2 downloads directories and 2 sstate-cache
directories: one in /poky and a second one in /poky/build/toaster. Toaster
projects use the ones in /poky/build/toaster, but it looks like the
Command Line Builds project uses the ones in poky. I think this is somehow
inconsistent.

I can leave with 1, but I am not sure we should do 2. I would rather have
all builds using the same sstate-cache and downloads directories.

Just my 2 cents.

Thanks!

Belén

>
>
>toaster log files, the sqlite database, _toaster_clones, all go into
>TOASTER_DIR=$BUILDDIR/toaster
>
>
>The goal is to make it more contained and to be sure that we can write to
>the dir.  for instance, if I am in /home/me and i do
>./poky/oe-init-build-env .; . toaster start; toaster tries to write to
>/home...
>
>
>2) the results of runbuilds log goes into a
>TOASTER_DIR/toaster_runbuilds.log
>this way it won't spew stuff into where we try to do cli builds
>
>
>Better ideas?
>
>
>-b
>an Intel employee
>