From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH v2 3/3] meta: rename isar-bitbake.conf to bitbake.conf
Date: Mon, 10 Dec 2018 11:22:47 +0100 [thread overview]
Message-ID: <20181210102247.27538-4-claudius.heine.ext@siemens.com> (raw)
In-Reply-To: <20181210102247.27538-1-claudius.heine.ext@siemens.com>
From: Claudius Heine <ch@denx.de>
With current bitbake versions it reads the 'bitbake.conf' from the
'conf' directory of a layer. So no copying is necessary.
Signed-off-by: Claudius Heine <ch@denx.de>
---
meta/conf/{isar-bitbake.conf => bitbake.conf} | 0
scripts/isar-setup-builddir | 9 ---------
2 files changed, 9 deletions(-)
rename meta/conf/{isar-bitbake.conf => bitbake.conf} (100%)
diff --git a/meta/conf/isar-bitbake.conf b/meta/conf/bitbake.conf
similarity index 100%
rename from meta/conf/isar-bitbake.conf
rename to meta/conf/bitbake.conf
diff --git a/scripts/isar-setup-builddir b/scripts/isar-setup-builddir
index d344148..227ab01 100755
--- a/scripts/isar-setup-builddir
+++ b/scripts/isar-setup-builddir
@@ -105,15 +105,6 @@ EOM
SHOWYPDOC=yes
fi
-cat <<EOF > $BUILDDIR/conf/bitbake.conf
-# ********************************************
-# THIS FILE IS GENERATED! DO NOT MESS WITH IT!
-# ********************************************
-
-EOF
-cat "$ISARROOT/meta/conf/isar-bitbake.conf" >> \
- "$BUILDDIR/conf/bitbake.conf"
-
# Ending the first-time run message. Show the no documentation banner.
if [ ! -z "$SHOWYPDOC" ]; then
cat <<EOM
--
2.19.2
next prev parent reply other threads:[~2018-12-10 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 9:52 [PATCH 0/2] Clean bitbake.conf and allow DL_DIR from env Harald Seiler
2018-11-27 9:53 ` [PATCH 1/2] meta: Only use isar's own bitbake.conf Harald Seiler
2018-12-07 14:30 ` Jan Kiszka
2018-12-10 9:31 ` Claudius Heine
2018-12-10 9:32 ` Jan Kiszka
2018-11-27 9:54 ` [PATCH 2/2] meta: Allow setting DL_DIR from environment Harald Seiler
2018-12-10 10:22 ` [PATCH v2 0/3] Clean bitbake.conf and allow DL_DIR from env claudius.heine.ext
2018-12-10 10:22 ` [PATCH v2 1/3] meta: Only use isar's own bitbake.conf claudius.heine.ext
2018-12-10 10:25 ` Harald Seiler
2018-12-10 10:22 ` [PATCH v2 2/3] meta: Allow setting DL_DIR from environment claudius.heine.ext
2018-12-10 10:22 ` claudius.heine.ext [this message]
2018-12-10 12:05 ` [PATCH v2 0/3] Clean bitbake.conf and allow DL_DIR from env 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=20181210102247.27538-4-claudius.heine.ext@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=ch@denx.de \
--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