public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: chombourger@gmail.com
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/2] bitbake.conf: add MACHINE to DEPLOY_DIR_IMAGE
Date: Wed, 21 Nov 2018 00:44:34 -0800 (PST)	[thread overview]
Message-ID: <867cd86e-92ff-4bad-8a51-4701021d43ed@googlegroups.com> (raw)
In-Reply-To: <b58541bc-c501-376d-c7a3-8a781c83a026@siemens.com>


[-- Attachment #1.1: Type: text/plain, Size: 281 bytes --]


>
> > Or rather something like 
> ${DEPLOY_DIR}/bootstrap-${DISTRO}-${DISTRO_ARCH} ? 
>
> Yes, makes sense. 
>
>
After taking a closer look, your proposal makes more sense as the bootstrap 
recipes already use DISTRO/HOST variables to construct the name of the 
output directory 

[-- Attachment #1.2: Type: text/html, Size: 465 bytes --]

  reply	other threads:[~2018-11-21  8:44 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
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 [this message]
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=867cd86e-92ff-4bad-8a51-4701021d43ed@googlegroups.com \
    --to=chombourger@gmail.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