public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] bitbake.conf: add MACHINE to DEPLOY_DIR_IMAGE
Date: Tue, 13 Nov 2018 08:52:00 +0100	[thread overview]
Message-ID: <72f412ad-018d-0c56-1a30-b2a6d99e7247@siemens.com> (raw)
In-Reply-To: <1541792023-514-3-git-send-email-Cedric_Hombourger@mentor.com>

On 09.11.18 20:33, Cedric Hombourger wrote:
> Align with OpenEmbedded and place image artifacts in a <machine> folder
> in tmp/deploy/images/.
> 
> Suggested-by: Jan Kiszka <jan.kiszka@siemens.com>
> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> ---
>   RECIPE-API-CHANGELOG.md     | 5 +++++
>   meta/conf/isar-bitbake.conf | 1 +
>   2 files changed, 6 insertions(+)
> 
> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> index c7b7552..95a5f96 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -6,6 +6,11 @@ Baseline: Release v0.5
>   Upcoming changes (v0.7)
>   -----------------------
>   
> +### location of image artifacts
> +
> +Align with OpenEmbedded and place image artifacts in a per-machine folder placed
> +in tmp/deploy (to avoid collisions among other things).
> +
>   ### more consistent artifact names
>   
>   multiconfig image artifacts are all placed in tmp/deploy/images. They include
> diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/isar-bitbake.conf
> index 666c4a3..d552c03 100644
> --- a/meta/conf/isar-bitbake.conf
> +++ b/meta/conf/isar-bitbake.conf
> @@ -19,6 +19,7 @@
>   # OTHER DEALINGS IN THE SOFTWARE.
>   
>   WORKDIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PF}"
> +DEPLOY_DIR_IMAGE = "${DEPLOY_DIR}/images/${MACHINE}"
>   DL_DIR = "${TOPDIR}/downloads"
>   SSTATE_DIR ?= "${TMPDIR}/sstate-cache"
>   BUILDCHROOT_HOST_DIR = "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot-host/rootfs"
> 

Thanks for picking this up! Looks good.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-11-13  7:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 19:33 [PATCH 0/2] " Cedric Hombourger
2018-11-09 19:33 ` [PATCH 1/2] start_vm: get DEPLOY_DIR_IMAGE from bitbake Cedric Hombourger
2018-11-09 19:33 ` [PATCH 2/2] bitbake.conf: add MACHINE to DEPLOY_DIR_IMAGE Cedric Hombourger
2018-11-13  7:52   ` Jan Kiszka [this message]
2018-11-21  8:10     ` Jan Kiszka
2018-11-21  8:13       ` chombourger
2018-11-21  8:18         ` chombourger
2018-11-21  8:19           ` Jan Kiszka
2018-11-21  8:39             ` chombourger
2018-11-21  9:06               ` Jan Kiszka
2018-11-21  9:08                 ` Jan Kiszka
2018-11-21  9:17                   ` chombourger
2018-11-21  9:35                 ` [PATCH] bootstrap: move to tmp/deploy/bootstrap Cedric Hombourger
2018-11-21 14:48                   ` Jan Kiszka
2018-11-23 10:23                   ` Maxim Yu. Osipov
2018-11-21  8:20         ` [PATCH 2/2] bitbake.conf: add MACHINE to DEPLOY_DIR_IMAGE Jan Kiszka
2018-11-21  8:44           ` chombourger
2018-11-14  3:20 ` [PATCH 0/2] " 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=72f412ad-018d-0c56-1a30-b2a6d99e7247@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