| Age | Commit message (Collapse) | Author | Files |
|---|
|
If configure is re-ran on an existing build tree the string substitutions we
need are done twice, resulting in invalid paths. Anchor the expressions so they
only match a pristine configure.ac.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Some items were listed multiple times in DEPENDS, avoid this situation.
Note, PR was not incremented as no change to the build process occurs.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Add pythonnative to the inherits list
Signed-off-by: Morgan Little <morgan.little@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Some place pnum=1 is used which is removed as well since
striplevel=1 is default
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
|
log.do_package:
NOTE: the following files were installed but not shipped in any package:
NOTE: /usr/lib/libxcb-dri2.so.0
NOTE: /usr/lib/libxcb-dri2.so.0.0.0
NOTE: libxcb-dev contains dangling symlink to
/usr/lib/libxcb-dri2.so.0.0.0
Then because of the dangling symlink, ldconfig fails at the time of
rootfs creation of image.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Add more detailed SUMMARY and DESCRIPTIONS to various graphics and
graphics related components. I've recently gotten question from users
what something is, or why it was needed.. this should go a long way toward
answering those questions.
Many of the descriptions were taken directly from the upstream location,
where one was not available the Debian packages were consulted for
information.
Signed-off-by: Mark Hatle <mark.hatle@windriver.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>
|
