From: <anders.roxell@gmail.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Anders Roxell <anders.roxell@enea.com>
Subject: [PATCH 1/2] oe-setup-builddir: Possibility to customize text.
Date: Wed, 27 Mar 2013 14:46:22 +0100 [thread overview]
Message-ID: <1364391983-9919-2-git-send-email-anders.roxell@gmail.com> (raw)
In-Reply-To: <1364391983-9919-1-git-send-email-anders.roxell@gmail.com>
From: Anders Roxell <anders.roxell@enea.com>
Possibility to customize the text that is presented to the user when
they execute the script.
Signed-off-by: Anders Roxell <anders.roxell@enea.com>
Tested-by: Maxin B. John <maxin.john@enea.com>
---
scripts/oe-setup-builddir | 16 ++++++----------
1 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
index 560453e..be5811d 100755
--- a/scripts/oe-setup-builddir
+++ b/scripts/oe-setup-builddir
@@ -55,6 +55,7 @@ if [ "x" != "x$TEMPLATECONF" ]; then
fi
OECORELAYERCONF="$TEMPLATECONF/bblayers.conf.sample"
OECORELOCALCONF="$TEMPLATECONF/local.conf.sample"
+ OECORENOTESCONF="$TEMPLATECONF/conf-notes.txt"
fi
if [ "x" = "x$OECORELOCALCONF" ]; then
@@ -113,14 +114,9 @@ cat <<EOM
You can now run 'bitbake <target>'
-Common targets are:
- core-image-minimal
- core-image-sato
- meta-toolchain
- meta-toolchain-sdk
- adt-installer
- meta-ide-support
-
-You can also run generated qemu images with a command like 'runqemu qemux86'
-
EOM
+if [ "x" = "x$OECORENOTESCONF" ]; then
+ OECORENOTESCONF="$OEROOT/meta/conf/conf-notes.txt"
+fi
+cat $OECORENOTESCONF
+unset OECORENOTESCONF
--
1.7.5.4
next prev parent reply other threads:[~2013-03-27 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 13:46 [RFC][PATCH 0/2] Add support for customizing help text when running oe-init-build-env anders.roxell
2013-03-27 13:46 ` anders.roxell [this message]
2013-03-27 13:46 ` [PATCH 2/2] conf-notes.txt: add the customized text file anders.roxell
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=1364391983-9919-2-git-send-email-anders.roxell@gmail.com \
--to=anders.roxell@gmail.com \
--cc=anders.roxell@enea.com \
--cc=openembedded-core@lists.openembedded.org \
/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