On Wednesday 14 March 2012 08:12:23 Darren Hart wrote:
> Perhaps. ALLOW_EMPTY is not defined in poky/documentation/* nor in
> poky/conf/documentation.conf.
> 
> (I realize this oe-core and not poky, but this is the best reference I
> know of)
> 
> Could you provide a terse description of how ALLOW_EMPTY* is meant to be
> used, its effects, and any needful cautionary text? Scott can then add
> it to the above documentation.

ALLOW_EMPTY (which like all package-controlling variables should always be 
used in conjunction a package name override, e.g. ALLOW_EMPTY_${PN}) just 
specifies that empty packages are actually produced instead of the default 
behaviour where they are skipped. This is mostly useful where there is an 
RDEPENDS or other runtime hard-requirement on the package existing.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to