2010/3/19 Richard Purdie <[email protected]>: > On Fri, 2010-03-19 at 11:09 +0100, Koen Kooi wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 19-03-10 10:29, Paul Menzel wrote: >> > Am Mittwoch, den 17.03.2010, 21:22 +0100 schrieb Steffen Sledz: >> > >> > […] >> > >> >> diff --git a/recipes/libunwind/libunwind.inc >> >> b/recipes/libunwind/libunwind.inc >> >> new file mode 100644 >> >> index 0000000..8513dc2 >> >> --- /dev/null >> >> +++ b/recipes/libunwind/libunwind.inc >> >> @@ -0,0 +1,13 @@ >> >> +DESCRIPTION = "a portable and efficient C programming interface (API) to >> >> determine the call-chain of a program" >> >> +DEPENDS = "" >> > >> > Remove this empty variable? >> >> I think that's meant to do what INHIBIT_DEFAULT_DEPS does, but I'm not sure. > > FWIW, it won't do that. It does appear to be totally purposeless.
Triggered by this discussion and having a few minutes to spare while
waiting for a test to complete, I did a quick grep on *.bbclass to
find out how many vars there are out there. I only counted uppercase
vars, so not things like ${bindir}. And ofc some of the vars are
probably not for public usage.
I was left with about 380 vars. See the list attached.
Guess most of them are undocumented (and actually 380 seems an awful lot to me).
Not sure if this is useful, but decided to pass it on anyway
(and if you don't like it just hit delete :-) )
Frans
vars
Description: Binary data
_______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
