public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH v2] meta-isar: update conf-notes.txt to display multiconfig patterns
Date: Fri, 29 Jun 2018 15:14:12 +0200	[thread overview]
Message-ID: <20180629131412.17853-1-henning.schild@siemens.com> (raw)
In-Reply-To: <20180628150510.13430-1-henning.schild@siemens.com>

bitbake without a multiconfig does not actually work anymore, update the
examples we provide the user when entering the build env.

Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
 doc/user_manual.md            | 3 ++-
 meta-isar/conf/conf-notes.txt | 5 +++--
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index 55261bf..9123587 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -116,7 +116,8 @@ DISTRO_ARCH ??= "armhf"
 Then, call `bitbake` with image names, e.g.:
 
 ```
-bitbake isar-image-base isar-image-debug
+bitbake multiconfig:qemuamd64-stretch:isar-image-base \
+        multiconfig:qemuamd64-stretch:isar-image-debug
 ```
 
 The following images are created:
diff --git a/meta-isar/conf/conf-notes.txt b/meta-isar/conf/conf-notes.txt
index 3ad220a..97c3086 100644
--- a/meta-isar/conf/conf-notes.txt
+++ b/meta-isar/conf/conf-notes.txt
@@ -1,3 +1,4 @@
 Common targets are:
-    isar-image-base
-    isar-image-debug
+    multiconfig:qemuamd64-stretch:isar-image-base
+    multiconfig:qemui386-jessie:isar-image-base
+    multiconfig:rpi-jessie:isar-image-base
-- 
2.16.4


  parent reply	other threads:[~2018-06-29 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 15:05 [PATCH] " Henning Schild
2018-06-29  9:36 ` Maxim Yu. Osipov
2018-06-29 13:14 ` Henning Schild [this message]
2018-06-29 13:20   ` [PATCH v2] " 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=20180629131412.17853-1-henning.schild@siemens.com \
    --to=henning.schild@siemens.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