From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Brad Litterell <brad@evidence.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: Developing in Python for Bitbake
Date: Tue, 17 Dec 2013 20:31:33 +0000 [thread overview]
Message-ID: <1688455.phEaOq5Cul@helios> (raw)
In-Reply-To: <E51394554A503C4E852F9BEE46B03E8D019AC817@TI-THOR.tasernet.com>
Hi Brad,
On Tuesday 17 December 2013 20:11:18 Brad Litterell wrote:
> I want to create a new bbclass for some internal build tooling and am fairly
> new to Python, so I have a couple of (hopefully quick) questions:
>
> 1. Can you recommend an Python IDE for developing for bitbake on Linux?
> There seem to be several, and if there is a consensus among the bitbake
> developers, I thought I'd start there.
I expect most people who work on BitBake don't use an IDE - just a text
editor, and we probably all use different ones. I myself mostly use Kate (from
KDE) which does provide syntax highlighting and completion though; at the
command line I also use vi.
> 2. Is there a list of pre-defined variables? For example, gitpkgv.bbclass
> starts with def get_git_pkgv(d, use_tags):
There's no reference for this level of things other than the code, I'm afraid,
but we're more than happy to answer questions if you have any.
> "d" appears to be frequently assumed. I'm guessing it is the same as the
> "D" variable in the recipes, but I am not sure whether there is a document
> that verifies this - and what else is available, or whether it is just
> tribal knowledge?
d is the data dictionary, as defined in bitbake/lib/bb/data_smart.py. d is not
related to the "D" variable in OpenEmbedded (although just as with any other
variable you can of course use d.getVar('D', True) to access it).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-12-17 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 20:11 Developing in Python for Bitbake Brad Litterell
2013-12-17 20:31 ` Paul Eggleton [this message]
2013-12-17 21:56 ` Brad Litterell
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=1688455.phEaOq5Cul@helios \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=brad@evidence.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.