From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Hongxu Jia <hongxu.jia@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] list-packageconfig-flags.py: fix searching bitbake module failed
Date: Thu, 29 Aug 2013 16:25:59 +0100 [thread overview]
Message-ID: <2059010.0EkyrxoSPo@helios> (raw)
In-Reply-To: <08dbbf71b281261919744307654a91bf3d452d18.1377660850.git.hongxu.jia@windriver.com>
On Wednesday 28 August 2013 12:30:01 Hongxu Jia wrote:
> Run list-packageconfig-flags.py on wrlinux's platform in which
> the oe-core layer and bitbake layer in different directories:
> ----
> ../layers/oe-core/scripts/contrib/list-packageconfig-flags.py
> Traceback (most recent call last):
> File "../layers/oe-core/scripts/contrib/list-packageconfig-flags.py", line
> 28, in <module> import bb.cache
> ImportError: No module named bb.cache
> ----
>
> The script import bb module from bitbake lib dir, the previous
> lib dir was hardcode and only worked on poky but not for others.
>
> In this situation, look for bitbake/bin dir in PATH could fix this issue.
>
> [YOCTO #5060]
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
> scripts/contrib/list-packageconfig-flags.py | 32
> ++++++++++++++++++++++------- 1 file changed, 25 insertions(+), 7
> deletions(-)
>
> diff --git a/scripts/contrib/list-packageconfig-flags.py
> b/scripts/contrib/list-packageconfig-flags.py index 149922d..371033a 100755
> --- a/scripts/contrib/list-packageconfig-flags.py
> +++ b/scripts/contrib/list-packageconfig-flags.py
> @@ -23,8 +23,26 @@ import sys
> import getopt
> import os
>
> +def search_bitbakepath():
> + bitbakepath = ""
> +
> + # Search path to bitbake lib dir in order to load bb modules
> + if os.path.exists(os.path.join(os.path.dirname(sys.argv[0]),
> '../../bitbake/lib/bb')): + bitbakepath =
> os.path.join(os.path.dirname(sys.argv[0]), '../../bitbake/lib') +
> bitbakepath = os.path.abspath(bitbakepath)
> + else:
> + # Look for bitbake/bin dir in PATH
> + for pth in os.environ['PATH'].split(':'):
> + if os.path.exists(os.path.join(pth, '../lib/bb')):
> + bitbakepath = os.path.abspath(os.path.join(pth, '../lib'))
> + break
> + if not bitbakepath:
> + sys.stderr.write("Unable to find bitbake by searching parent
> directory of this script or PATH\n") + sys.exit(1)
> + return bitbakepath
> +
> # For importing the following modules
> -sys.path.insert(0,
> os.path.join(os.path.abspath(os.path.dirname(sys.argv[0])),
> '../../bitbake/lib'))
> +sys.path.insert(0, search_bitbakepath())
This looks fine, but I've been thinking for a while that we should have a place
for shared library code just for the scripts directory in which we could put
this function rather than having it repeated in a number of different scripts.
I'll add an enhancement to bugzilla to do this in 1.6.
> import bb.cache
> import bb.cooker
> import bb.providers
> @@ -39,12 +57,12 @@ OPTION:
> -p, --prefer list pkgs with preferred version
>
> EXAMPLE:
> -list-packageconfig-flags.py poky/meta poky/meta-yocto
> -list-packageconfig-flags.py -f poky/meta poky/meta-yocto
> -list-packageconfig-flags.py -a poky/meta poky/meta-yocto
> -list-packageconfig-flags.py -p poky/meta poky/meta-yocto
> -list-packageconfig-flags.py -f -p poky/meta poky/meta-yocto
> -list-packageconfig-flags.py -a -p poky/meta poky/meta-yocto
> +list-packageconfig-flags.py
> +list-packageconfig-flags.py -f
> +list-packageconfig-flags.py -a
> +list-packageconfig-flags.py -p
> +list-packageconfig-flags.py -f -p
> +list-packageconfig-flags.py -a -p
> '''
>
> def usage():
Acked-by: Paul Eggleton <paul.eggleton@linux.intel.com>
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-08-29 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 4:30 [PATCH 0/1] list-packageconfig-flags.py: fix searching bitbake module failed Hongxu Jia
2013-08-28 4:30 ` [PATCH 1/1] " Hongxu Jia
2013-08-29 15:25 ` 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=2059010.0EkyrxoSPo@helios \
--to=paul.eggleton@linux.intel.com \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.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