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

[Alexander Smirnov <asmirnov@ilbers.de>]

On 12/12/2017 11:01 AM, Christian Storm wrote:
>> [...]
>> BTW: why can't you add this hack to 'build.sh', after
>> 'dpkg-buildpackage' complete, just run 'dpkg -i' on newly baked
>> packages. Also ugly, but no headache with deps parsing. :-)
> 
> Yes, could do that, for the time being. But this installs each and every
> package into the buildchroot, I just need one. However, I think I go for
> this to not loose contact to -next's HEAD.
> 
>>>     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?
>>
>> Probably I get the possible issue. How do you add packages A and B to
>> the build chain, via IMAGE_INSTALL? If so, where do you set
>> IMAGE_INSTALL variable?
> 
> I do have a meta-mylayer/recipes-core/images/image-mybox.bb in which I
> do IMAGE_INSTALL_append = " B"
>

I think that's the problem with current series. I assume that 
IMAGE_INSTALL is global variable, like in pure Isar where it's set in 
'local.conf' file. If you append IMAGE_INSTALL locally in recipe, this 
changes won't be seen in buildchroot recipe, so

DEPENDS += "${IMAGE_INSTALL}"

makes no sense.

Ok, will drop it.

Alex