From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: Chandana kalluri <ckalluri@xilinx.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
Mark Hatle <mhatle@xilinx.com>
Subject: Re: [yocto] RFC: Devtool support to read BB_ENV_EXTRAWHITE variables and parse the env variables same as bitbake
Date: Thu, 23 Jul 2020 16:05:36 +1200 [thread overview]
Message-ID: <7843669.NyiUUSuA9g@linc> (raw)
In-Reply-To: <BYAPR02MB5926CA0B969618BE28ADC824B0790@BYAPR02MB5926.namprd02.prod.outlook.com>
Hi Chandana,
On Thursday, 23 July 2020 11:29:24 NZST Chandana kalluri wrote:
> I have a use case where the user passes path to devtool modify using TOPDIR.
> Ex. devtool modify linux-xlnx -n ${TOPDIR}/linux-xlnx
>
> Since devtool doesn't evaluate TOPDIR as bitbake variable, during expansion
> it expands it as devtool modify linux-xlnx -n /linux-xlnx
Assuming you are quoting the command verbatim, the issue here is that the
shell is evaluating TOPDIR, so devtool doesn't even get to see the reference.
Granted, even if you use single quotes to prevent the shell expansion, devtool
does not expand the variable reference; it could be made to fairly easily
though.
> Can we add support to devtool that reads BB_ENV_EXTRAWHITE variable and
> parse the env variables same as bitbake ?
I can see how this might be related but it doesn't seem necessary for the
expansion to work - it would only be needed if you wanted to pass in TOPDIR
externally, but that would have other implications as well. Is that needed?
Cheers
Paul
prev parent reply other threads:[~2020-07-23 4:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 23:29 RFC: Devtool support to read BB_ENV_EXTRAWHITE variables and parse the env variables same as bitbake Chandana kalluri
2020-07-23 4:05 ` Paul Eggleton [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=7843669.NyiUUSuA9g@linc \
--to=bluelightning@bluelightning.org \
--cc=ckalluri@xilinx.com \
--cc=mhatle@xilinx.com \
--cc=yocto@lists.yoctoproject.org \
/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