| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
(From OE-Core rev: aca5eb8cda9a26b5bb9c2f1e45f2e5c1af643da0)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
to rebuild after perl upgrade
* this isn't probably complete list.. just what failed here
(From OE-Core rev: f586aaa8d00361a9597a546d665077c75cf4d520)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It's not appropriate to require xxx.bb in xxx-native.bb, causing that
xxx-native depends on target recipe.
Use BBCLASSEXTEND to solve this issue.
(From OE-Core rev: aa8f6b64055c6576bcdb63d3bbf9ab47b87c0d59)
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
On hosts where we may already be past the #! limit this is required
and this is safe on the target as well. This is be7fe31 in oe.dev.
Related to this we now bump all PRs for recipes that inherit cpan.
Note that in oe.dev we mangle for perl but here we use the new
nativeperl script.
(From OE-Core rev: 682a213dc732074985bf86f508305fc6eafe18d9)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
| |
|
|
| |
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
|
| |
|
|
|
|
|
|
| |
for hostperl needing to load .so files (for module scalar::util) the host/native
perl library path is placed 1st in the @INC with the -I parameter to perl.
Otherwise hostperl gives error can not load module scalar::util.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
| |
|
|
| |
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
| |
|
|
|
|
| |
Add README file checksu to bb file
Signed-off-by: Mei Lei <lei.mei@intel.com>
|
|
|
Having one monolithic packages directory makes it hard to find things
and is generally overwhelming. This commit splits it into several
logical sections roughly based on function, recipes.txt gives more
information about the classifications used.
The opportunity is also used to switch from "packages" to "recipes"
as used in OpenEmbedded as the term "packages" can be confusing to
people and has many different meanings.
Not all recipes have been classified yet, this is just a first pass
at separating things out. Some packages are moved to meta-extras as
they're no longer actively used or maintained.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
