public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3] Replace ISARROOT with more relevant variables
Date: Thu, 17 Sep 2020 08:15:50 +0530	[thread overview]
Message-ID: <CALLGG_LGiv+8aFLn4M8mE7jKvqccCT2Kgz6=kJGscD4V-ySq+A@mail.gmail.com> (raw)
In-Reply-To: <20200916191157.GG16317@yssyq.m.ilbers.de>

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

On Thu, 17 Sep 2020 at 12:42 AM, Baurzhan Ismagulov <ibr@radix50.net> wrote:

> Hello Vijai Kumar,
>
>
>
> thanks for updating the wic series. Could you please also rebase this one?


Sure Baurzhan. I will work on this and send it today.

Thanks,
Vijai Kumar K


>
>
>
> With kind regards,
>
> Baurzhan.
>
>
>
>
>
> On Mon, Apr 27, 2020 at 03:58:37PM +0530, Vijai Kumar K wrote:
>
> > 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.
>
>
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "isar-users" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to isar-users+unsubscribe@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/20200916191157.GG16317%40yssyq.m.ilbers.de
> .
>
>

[-- Attachment #2: Type: text/html, Size: 2530 bytes --]

      reply	other threads:[~2020-09-17  2:46 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
2020-09-16 19:11             ` Baurzhan Ismagulov
2020-09-17  2:45               ` vijai kumar [this message]

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='CALLGG_LGiv+8aFLn4M8mE7jKvqccCT2Kgz6=kJGscD4V-ySq+A@mail.gmail.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