what is the 'd' variable in bitbake recipes?

GoogleGroups
1

This is proving incredibly hard to google for since searching for ‘d’ aliases to so many things. Do you guys know where I can find documentation about this variable?

2

http://docs.openembedded.org/usermanual/usermanual.html

The above documentation should clear your query

3

Do you mean -D or -d – Tells BitBake where to install the completed application and its files in preparation for packaging.

4

Don:
I’m not talking about an argument to bitbake, but a variable that seems to exist in the context of all .bb files execution.

Victor:
It’s not documented in that manual either but I think it might be a shortcut to bb.data
I think it’s some ‘datasmart’ variable that aggregates passed in arguments from various other bitbake recipes.

example :

d.getVar('PN', True)
5

Maybe this is what you mean. Found in the manual
NOTE:
This is only supported in .bb and .bbclass files.
def get_depends(bb, d):
if bb.data.getVar('SOMECONDITION', d, 1):
return "dependencywithcond"
else:
return "dependency"
SOMECONDITION
= "1"
DEPENDS
= "${@get_depends(bb, d)}"
This would result in
DEPENDS
containing
dependencywithcond

6

I would ask on the OpenEmbedded mailing list for the correct answer, the
other answers currently given are wrong. The bitbake manual will be the
best place to find the answer on your own, however it is significantly
dated at the moment.

====+GUESS+====
I imagine d is an object which represents a recipe. As it is a variable
though, it could really be anything and possibly different depending on
the context.
====+GUESS+====

Cheers,
Jack.

7

Please do not give this link out, it refers to OpenEmbedded Classic and
as such is depreciated.

8

i'm pretty sure it's simply the global "data dictionary", which
keeps track of all of the relevant variables and their values.

rday