From: Vijai Kumar K <vijaikumar.kanagarajan@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: vijaikumar.kanagarajan@gmail.com, isar-users@googlegroups.com,
henning.schild@siemens.com, claudius.heine.ext@siemens.com
Subject: Re: [PATCH v2] isar-init-build-env: Always set ISARROOT
Date: Mon, 30 Sep 2019 12:16:55 +0530 [thread overview]
Message-ID: <20190930064655.GA10223@lightning> (raw)
In-Reply-To: <c4f2a0de-351a-aad3-fce5-4076a4ab2dbc@siemens.com>
On Mon, Sep 30, 2019 at 08:06:14AM +0200, Jan Kiszka wrote:
> On 27.09.19 23:43, vijaikumar.kanagarajan@gmail.com wrote:
> > From: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
> >
> > When switching between two ISAR workspaces in the same shell
> > session, the ISARROOT setting of the previous workspace would be
> > picked up for the new workspace resulting in an incorrect
> > configuration.
> >
> > Always set ISARROOT irrespective of whether it is empty or not.
> >
> > Signed-off-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
> > ---
> > Changes in v2:
> > - Remove redundant code
> >
> > isar-init-build-env | 7 ++-----
> > 1 file changed, 2 insertions(+), 5 deletions(-)
> >
> > diff --git a/isar-init-build-env b/isar-init-build-env
> > index b08bb59..404efcb 100755
> > --- a/isar-init-build-env
> > +++ b/isar-init-build-env
> > @@ -42,13 +42,10 @@ if [ -z "$ZSH_NAME" ] && [ "$0" = "$THIS_SCRIPT" ]; then
> > exit 1
> > fi
> > -if [ -z "$ISARROOT" ]; then
> > - ISARROOT=$(dirname "$THIS_SCRIPT")
> > - ISARROOT=$(readlink -f "$ISARROOT")
> > -fi
> > +ISARROOT=$(dirname "$THIS_SCRIPT")
> > +ISARROOT=$(readlink -f "$ISARROOT")
> > unset THIS_SCRIPT
> > -ISARROOT=$(readlink -f "$ISARROOT")
> > export ISARROOT
> > . "$ISARROOT/scripts/isar-buildenv-internal" "$1" && \
> > TEMPLATECONF="$TEMPLATECONF" "$ISARROOT/scripts/isar-setup-builddir" || {
> >
>
> OE is doing the same, i.e. does not update OEROOT on second execution. This
> allows to set OEROOT prior to calling the script (https://github.com/openembedded/openembedded-core/commit/3327e2a9222004d8ac7974cb1d9fe77c81176cfc).
Yes. But then OE also unsets OEROOT later in that script.
But with our below change we are no longer doing the same.
https://github.com/ilbers/isar/commit/b59cf9ef8aae682937e8a4a5cda1c6d080d329b7
Thanks,
Vijai Kumar K
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-09-30 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 21:38 [PATCH] " vijaikumar.kanagarajan
2019-09-27 21:43 ` [PATCH v2] " vijaikumar.kanagarajan
2019-09-30 6:06 ` Jan Kiszka
2019-09-30 6:46 ` Vijai Kumar K [this message]
2019-09-30 7:01 ` Jan Kiszka
2019-09-30 7:49 ` Vijai Kumar K
2019-12-11 10:14 ` vijai kumar
2019-12-17 12:24 ` Baurzhan Ismagulov
2019-12-24 5:21 ` vijai kumar
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=20190930064655.GA10223@lightning \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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