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
Please do not give this link out, it refers to OpenEmbedded Classic and
as such is depreciated.
On 11/11/13 05:10, sanchayan maity wrote:
http://docs.openembedded.org/usermanual/usermanual.html
The above documentation should clear your query
On Mon, Nov 11, 2013 at 10:35 AM, Neabex
On Tue, 12 Nov 2013, Jack Mitchell wrote:
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.
i'm pretty
http://docs.openembedded.org/usermanual/usermanual.html
The above documentation should clear your query
On Mon, Nov 11, 2013 at 10:35 AM, Neabex nick.g...@gmail.com wrote:
This is proving incredibly hard to google for since searching for 'd'
aliases to so many things. Do you guys know where
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
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
