Re: Deployment for machine X will remove its results from machine Y's deploy dir

[Gary Thomas <gary@mlbassoc.com>]

On 2014-11-27 01:35, Mike Looijmans wrote:
> Here's an example recipe to demonstrate the issue. Save it as "deployme.bb" into a recipe dir. Then build it for two machines. Building it for one machine will remove it from the
> deployment directory of the other. This problem has been bugging me for months, I had files just "disappear" mysteriously from the deploy directory and seemingly random times, and
> now I finally figured out what causes it.
>
> (cut here)
>
> SUMMARY = "Demonstrate a bug in OE deployment"
> DESCRIPTION = "Build this package for a machine X, then look at the image's \
>   deploy directory. You'll see a deployme.txt there. Now build it for another \
>   machine, e.g. "Y". The deployme.txt for machine X will have disappeared \
>   from the image dir. This appears to be a bug in OE's deployment."
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690"
>
> inherit allarch deploy
>
> do_compile () {
>      echo "Hello world!" > deployme.txt
> }
>
> do_deploy () {
>      install -d ${DEPLOYDIR}
>      install -m 644 ${B}/deployme.txt ${DEPLOYDIR}/
> }
>
> addtask deploy before do_build after do_compile
>
> (cut here)

Very interesting & verified with the latest master.

Have you filed a bug?  https://bugzilla.yoctoproject.org/

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------