| Age | Commit message (Collapse) | Author | Files |
|---|
|
some unneeded complexity (from poky)
|
|
|
|
|
|
|
|
when multiple -dev or -dbg packages are generated and when a single one is generated (from poky)
|
|
|
|
certain dependency chainhandling in both ipkg and dpkg (from poky)
|
|
generate (PACKAGES != ) removing needless dependencies (from poky)
|
|
correct operation with bitbake 1.8.x. Old behaviour is maintained in a special legacy anonymous function in base.bbclass. The patch is an improved version of the one discussed on the mailing list.
|
|
|
|
- if package contain libraries which are not used outside then add PRIVATE_LIBS
variable with names of them to not generate shlibs for them.
|
|
"inherit package_ipk package_tar" and seems to interfere with do_split_packages
|
|
|
|
|
|
causing python
traceback spew during population
|
|
migration
|
|
|
|
I do not know does this is best way of fixing it but it is better to have it in
repository then having rootfs images without libc.
|
|
${HOST_PREFIX}objdump
package.bbclass : make use of the OBJDUMP variable rather than
calling ${BUILD_PREFIX}objdump inside do_shlibs. As the original
usage was faulty and ended up calling host objdump which works
for some arm targets but not all.
|
|
RRECOMMENDS, from Poky
* poky rev 823: 'package.bbclass: depchains: don't -destructively- set the pkg's RRECOMMENDS.'
* poky rev 824: 'base.bbclass: depchains: don't -destructively- set the pkg's RRECOMMENDS.'
|
|
packages. The way it selects the principle package name needs totally reworking as the current code is flawed but apply a workaround for now (this is unrelated to other changes to package.bbclass)
|
|
packages. The way it selects the principle package name needs totally reworking as the current code is flawed but apply a workaround for now (this is unrelated to other changes to package.bbclass)
|
|
then package_write which actually generates the packages. The two stage approach allows us to avoid circular dependency issues from classes like debian.bbclass. As the data being emitted into pkgdata/ changed, you need to either wipe tmp or rerun the do_package tasks (wipe the do_package stamps). Everything will repackage anyway due to the new task.
|
|
functional changes (from poky)
|
|
barfing
package.bbclass: likewise
|
|
* people should really watch out with introducing regressions
|
|
people are reporting
~lart kergoth for introducing this regression
|
|
* Add package "depchains". This facilitates, for example, ensuring that if
A depends upon B, then A-dev will RRECOMMENDS B-dev, and the same for the
-dbg packages.
|
|
other packages.
|
|
|
|
* Avoid premature use of the PKG_* variables. We don't need to make use of
the debian.bbclass (or otherwise) renamed package names until the very end
of the packaging. This was necessary in order to enhance my
depchain/correspondantdeps stuff, and doesn't seem to harm anything.
|
|
* Fix bug which caused non-detection.
* Make visible error message for such condition.
* But still recover and continue for now, while we don't
have all occurances fixed in metadata. Note that while
content of the package will be ok, metadata can be wrong.
So, recover behavior should not be relied upon, this going to
be fatal condition later.
Oked-by: RP, hrw
|
|
* Factor out "strippedness" substring as FILE_UNSTRIPPED_MATCH.
* Allow FILE_UNSTRIPPED_MATCH to be overriden, useful to support
other executable formats.
* Also, don't complain if .debug directory already exist
(can heppen if manually run BB tasks, e.g. for debugging).
|
|
Make legitimize_package_name also convert <U0123> style encoding of
unicode codepoints into their utf-8 representation, as in glibc locale
files.
|
|
|
|
package if we want
|
|
multithreading version of bitbake. Also, set BB_DEFAULT_TASK to specify the default task (build) rather than hardcode into bitbake.
|
|
|
|
Set PACKAGEFUNCS only once. Now if more than one bbclass inherits
package both additional functions will be executed. The new packagefuncs
will be appended to the list and the old ones will not be lost
|
|
that are stripped from binaries and the symbols are linked to the original binaries via the gnu-debuglink section.If the -dbg packages are installed, oprofile and gdb will use them for symbol lookup.
|
|
|
|
|
|
|
|
using qemu. based on a patch originally written by Phil Blundell. fixes hh.org Bug #1385 (localedef OOM issue).
- running localedef (in qemu...) for every locale takes a while. set
BINARY_LOCALE_ARCHES = "" to avoid the new behaviour.
|
|
package.bbclass now tracks any package renaming performed using PKG_*.
When a package is built, the runtime variables are translated using
this cached information which is stored in staging.
From now on, only use package names are valid in runtime variables like
RDEPENDS, RRECOMMENDS and RSUGGESTS. eg. fontconfig-dev is correct,
libfontconfig-dev would be wrong.
As debian.bbclass can't determine package renaming until after a
package's contents is known, the class has to set BUILD_ALL_DEPS = "1".
This also means OE is no longer forced into one package renaming scheme.
|
|
|
|
|
|
IGNORE_STRIP_ERRORS
|
|
- package.bbclass now uses file-native and cross strip to reliably strip
unstripped executables and check the return code. For the moment a
failure here doesn't cause the build to fail but does output a failure
message direct to the controlling terminal (this is temporary). This
behaviour can be changed by forcing IGNORE_STRIP_ERRORS = ""
The change works by using a new runstrip shell function for every
potentially strippable file. Since this calls native 'file' there is
a dependency on all inheritors of package.bbclass for file-native and
since this would break native builds (because of the cycle in
file-native and it's own native depends) native.bbclass cancels this
dependency (system file should be fine for native packages and, anyway
native currently doesn't package.)
|
|
failure.
|
