openembedded-core.git/meta/conf/documentation.conf, branch uninative-1.0

conf/documentation.conf: remove BBLAYERS_NON_REMOVABLE

2016-03-07T17:16:53+00:00

Hob was the only thing paying attention to this, and now Hob itself has
been removed we can remove this as well.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

documentation.conf: align the documentation for DEBUG_OPTIMIZATION and FULL_OPTIMIZATION with bitbake.conf

2016-02-02T17:48:00+00:00

Signed-off-by: Pascal Bach 
Signed-off-by: Richard Purdie

libc-package.bbclass: add LOCALE_UTF8_IS_DEFAULT

2016-01-29T17:31:51+00:00

python hard-codes the encoding of many locales; for instance, en_US is
always assumed to be ISO-8859-1, regardless of the actual encoding of
the en_US locale on the system. cf
https://hg.python.org/cpython/file/7841e9b614eb/Lib/locale.py#l1049,
getdefaultlocale(), etc. This code appears to date back to python 2.0.
The source of this hard-coding is Xorg's locale.alias but is ultimately
justified by glibc's SUPPORTED.

This causes problems on OE, because any locale lacking an explicit
encoding suffix (e.g. en_US) is UTF-8. It has been this way from the
beginning (svn r1). That is not a bug, per se -- no specification
prohibits this AFAIK. But it seems to be at odds with virtually every
other glibc-based distribution in existence. To avoid needlessly
aggravating hidden bugs that nobody else might hit, it makes sense to
disable this behavior such that locales are named precisely as specified
by SUPPORTED.

I suppose that reasonable minds may disagree on whether or not the
current behavior is prudent; at the very least, this is likely to break
IMAGE_LINGUAS settings. So let's create a new distro variable
LOCALE_UTF8_IS_DEFAULT to allow either behavior. Set it to 0 and all
your locales get named exactly like they are in SUPPORTED. Leave it at 1
to preserve current OE locale naming conventions.

Signed-off-by: Richard Tollerton 
Signed-off-by: Ross Burton

documentation.conf: Update the help for BBMASK

2016-01-29T17:02:53+00:00

Since it is now possible to concatenate multiple regular expressions
into BBMASK, there is no longer any real reason to limit it to be
specified only in local.conf.

Signed-off-by: Peter Kjellerstedt 
Signed-off-by: Richard Purdie

qt4: remove recipes and classes

2016-01-07T13:33:59+00:00

Qt4 is no longer supportd upstream, but it is still needed for LSB compliancy.
Qt4 recipes have been moved to a separate meta-qt4 layer to be consistent with
meta-qt3 and meta-qt5.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Ross Burton

lib/oe/image.py: Add image generation for companion debug filesystem

2015-10-02T23:01:35+00:00

The companion debug filesystem, enabled with IMAGE_GEN_DEBUGFS, was
creating the companion filesystem but was missing the code to actually
package it into a usable filesystem.

The code (and associated documentation) will allow the debugfs to generate a
companion tarball or other image.

Signed-off-by: Mark Hatle 
Signed-off-by: Richard Purdie

documentation: document KERNEL_CLASSES

2015-07-02T22:03:01+00:00

Signed-off-by: Ross Burton

documentation.conf: Document do_vmimg

2015-06-11T22:55:41+00:00

Changes due to new combined support for both vmdk and vdi files.

Signed-off-by: Juro Bystricky 
Signed-off-by: Ross Burton

BAD_RECOMMENDATIONS also works for RPM packaging.

2015-01-16T22:59:45+00:00

Signed-off-by: Robert P. J. Day 
Signed-off-by: Ross Burton

base/license.bbclass: expand wildcards in INCOMPATIBLE_LICENSE

2014-12-19T17:54:14+00:00

The whitelist processing in code in base.bbclass does not play well with
wildcards in INCOMPATIBLE_LICENSES. The code expects bad_licenses to
contain actual license names, not wildcards.

Add incompatible_license_contains to replace bb.utils.contains(
"INCOMPATIBLE_LICENSE", **, **, **, d)

[YOCTO #5592]

Signed-off-by: Hongxu Jia