From: Jan Kiszka <jan.kiszka@siemens.com>
To: cedric_hombourger@mentor.com, isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] classes/image: Separate image rootfs for machines
Date: Tue, 12 Mar 2019 06:13:15 +0100 [thread overview]
Message-ID: <60dc55f4-bac7-8284-d9aa-548286118f0c@siemens.com> (raw)
In-Reply-To: <992636ec-adb5-4669-9091-2eebb6d951fb@googlegroups.com>
On 11.03.19 20:43, cedric_hombourger@mentor.com wrote:
> That change above will still run the recipe multiple times,
> overwriting at least the logs in confusing ways, if not more, no?
>
>
> agreed. should we align with OE and have tmp/work/${DISTRO_ARCH}-${DISTRO},
> tmp/work/all-${DISTRO} and tmp/work/${MACHINE}-${DISTRO} instead of having
> everything land under tmp/work/${DISTRO}-${DISTRO_ARCH}/?
>
We just need to be careful not to destroy legitimate sharing of packages this
way, e.g. if I build one kernel for multiple target boards. I think we are way
ahead of OE in this regard with using multiconfig.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-03-12 5:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 17:03 [PATCH 0/1] " Maxim Yu. Osipov
2019-03-11 17:03 ` [PATCH 1/1] classes/image: " Maxim Yu. Osipov
2019-03-11 18:00 ` Jan Kiszka
2019-03-11 19:43 ` cedric_hombourger
2019-03-12 5:13 ` Jan Kiszka [this message]
2019-03-12 5:57 ` [PATCH] isar-image: use a per-machine WORKDIR for image builds Cedric Hombourger
2019-03-12 10:45 ` Maxim Yu. Osipov
2019-03-14 10:54 ` [PATCH 1/1] classes/image: Separate image rootfs for machines Baurzhan Ismagulov
2019-03-12 8:30 ` Maxim Yu. Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60dc55f4-bac7-8284-d9aa-548286118f0c@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox