From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] isar-setup-builddir script: remove copying multiconfigs
Date: Wed, 7 Feb 2018 13:45:41 +0100 [thread overview]
Message-ID: <93f6e3ee-2ae7-ed9c-a5fe-51897d3f9612@siemens.com> (raw)
In-Reply-To: <20180207090657.5299-1-claudius.heine.ext@siemens.com>
On 2018-02-07 10:06, [ext] claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> With the recent update of bitbake, copying the multiconfig files to the
> build dir is no longer necessary.
>
> Signed-off-by: Claudius Heine <ch@denx.de>
> ---
> scripts/isar-setup-builddir | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/scripts/isar-setup-builddir b/scripts/isar-setup-builddir
> index d400694..cabe732 100755
> --- a/scripts/isar-setup-builddir
> +++ b/scripts/isar-setup-builddir
> @@ -69,7 +69,6 @@ if [ -n "$TEMPLATECONF" ]; then
> ISARCORELAYERCONF="$TEMPLATECONF/bblayers.conf.sample"
> ISARCORELOCALCONF="$TEMPLATECONF/local.conf.sample"
> ISARCORENOTESCONF="$TEMPLATECONF/conf-notes.txt"
> - ISARMULTICONF="$TEMPLATECONF/multiconfig"
> fi
>
> unset SHOWYPDOC
> @@ -157,7 +156,3 @@ if [ -z "$ISARCORENOTESCONF" ]; then
> fi
> [ ! -r "$ISARCORENOTESCONF" ] || cat $ISARCORENOTESCONF
> unset ISARCORENOTESCONF
> -
> -if [ -d "$ISARMULTICONF" ]; then
> - cp -r "$ISARMULTICONF" $BUILDDIR/conf
> -fi
>
Looks good!
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-02-07 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 9:06 claudius.heine.ext
2018-02-07 12:45 ` Jan Kiszka [this message]
2018-02-07 18:19 ` Alexander Smirnov
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=93f6e3ee-2ae7-ed9c-a5fe-51897d3f9612@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@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