| Age | Commit message (Collapse) | Author | Files |
|---|
|
Originally approached with "package.bbclass: introduce KEEP_GNU_DEBUGLINK":
http://patchwork.openembedded.org/patch/886/
Redone with a change from INHIBIT_PACKAGE_STRIP to PACKAGE_STRIP which
allows more options. By default it does exactly the same thing as is done
today, strips the binary, but keeps the gnu.debuglink section. When set to
"no", stripping is not done at all, when set to "full" the gnu.debuglink
section is not re-added to the binary.
Signed-off-by: Roman I Khimov <khimov@altell.ru>
Acked-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Brijesh Singh <bksingh@ti.com>
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
Signed-off-by: Roger Monk <r-monk@ti.com>
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
Signed-off-by: Koen Kooi <k-kooi@ti.com>
|
|
* New codec recipes from Arago team in Germantown
* Updated dm6446 and dm355 from Brijesh Singh
* cmem, gst-ti and dmai fixes from Brijesh Singh
angstrom: introduce SOC_FAMILY and start using it TI recipes as a testing ground
* SOC_FAMILY tells you which system on chip is used in the MACHINE, e.g. omap3, dm355, pxa25x, s3c24xx.
This avoids having to duplicate lots of overrides in machine specific recipes. This is *NOT*
intended to be used as a package arch.
|
