public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3] Replace ISARROOT with more relevant variables
Date: Wed, 27 May 2020 22:28:02 -0700 (PDT)	[thread overview]
Message-ID: <82870cfb-cacf-4f15-89a2-b0e9b2213ec3@googlegroups.com> (raw)
In-Reply-To: <20200526075101.4iipq63ke245qrpn@yssyq.m.ilbers.de>


[-- Attachment #1.1: Type: text/plain, Size: 2354 bytes --]



On Tuesday, May 26, 2020 at 1:21:05 PM UTC+5:30, Baurzhan Ismagulov wrote:
>
> Hello Vijai Kumar, 
>
> On Mon, May 25, 2020 at 07:54:57PM -0700, vijai kumar wrote: 
> > Any review comments on this? 
>
> This looks good to me, sorry for the delay. I had held this because it 
> happens 
> to conflict with the hardlinking series which arrived earlier. However, 
> we've 
> newly discovered that the latter seems to have problems with its test 
> case, so 
> I tend to pick the one that could be applied first. 
>

Thanks for the update Baurzhan. Good to know its in pipeline.

BR,
Vijai Kumar K
 

>
> With kind regards, 
> Baurzhan. 
>
>
> > On Monday, April 27, 2020 at 3:59:07 PM UTC+5:30, vijai kumar wrote: 
> > > 
> > > From: Vijai Kumar K <Vijaikumar_...@mentor.com <javascript:>> 
> > > 
> > > 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. The user had to manually unset ISARROOT to avoid 
> > > any issues. 
> > > 
> > > As like OEROOT in OE, let us unset ISARROOT at the end of the 
> > > initialization script. This helps us to avoid the above issue 
> > > and also preserves support for passing ISARROOT from a caller 
> > > script as in OE. 
> > > 
> > > ISARROOT is used mostly to derive the location of bitbake, scripts, 
> > > testsuite, meta and meta-isar directories. 
> > > 
> > > Layers like meta, meta-isar already have their paths in LAYERDIR_core 
> > > and LAYERDIR_isar which can be used. For other directories introduce 
> > > dedicated variables BITBAKEDIR, SCRIPTSDIR and TESTSUITEDIR. 
> > > 
> > > Signed-off-by: Vijai Kumar K <Vijaikumar_...@mentor.com <javascript:>> 
>
> > > --- 
> > > Changes in v3: 
> > >     - Send patch using proper send. 
> > > Changes in v2: 
> > >     - Approach using dedicated variables for each commonly used 
> > > directories. 
> > > 
> > >  isar-init-build-env                      |  1 + 
> > >  meta/classes/image-sdk-extension.bbclass |  2 +- 
> > >  meta/classes/wic-img.bbclass             | 31 
> ++++++++++++------------ 
> > >  scripts/ci_build.sh                      | 12 +++++---- 
> > >  scripts/isar-buildenv-internal           |  7 ++++-- 
> > >  5 files changed, 30 insertions(+), 23 deletions(-) 
>

[-- Attachment #1.2: Type: text/html, Size: 3510 bytes --]

  reply	other threads:[~2020-05-28  5:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 19:35 [PATCH] Introduce SCRIPTSDIR variable Vijai Kumar K
2020-01-28 21:43 ` Henning Schild
2020-01-29  6:22   ` Vijai Kumar K
2020-02-18  6:05     ` vijai kumar
2020-04-05 16:49 ` Baurzhan Ismagulov
2020-04-06  8:30   ` vijai kumar
2020-04-23 14:56     ` vijai kumar
2020-04-27  9:11       ` [PATCH v2] Replace ISARROOT with more relevant variables Vijai Kumar K
2020-04-27 10:22         ` vijai kumar
2020-04-27 10:28           ` [PATCH v3] " Vijai Kumar K
2020-05-26  2:54             ` vijai kumar
2020-05-26  7:51               ` Baurzhan Ismagulov
2020-05-28  5:28                 ` vijai kumar [this message]
2020-09-16 19:11             ` Baurzhan Ismagulov
2020-09-17  2:45               ` 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=82870cfb-cacf-4f15-89a2-b0e9b2213ec3@googlegroups.com \
    --to=vijaikumar.kanagarajan@gmail.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