meta-openembedded/meta-multimedia
Khem Raj f8e3d25430 x265: Pass --debug-prefix-map to nasm
Ensures absolute source paths are not emitted into nasm assembled objects

Fixes
WARNING: x265-3.2.1-r0 do_package_qa: QA Issue: File /usr/lib/.debug/libx265.so.179 in package x265-dbg contains reference to TMPDIR [buildpaths]

Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 6ab0ca758a)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2023-05-28 16:42:01 -04:00
..
classes Convert to new override syntax 2021-08-03 10:21:25 -07:00
conf layer.conf: update LAYERSERIES_COMPAT for mickledore 2023-01-04 14:34:04 -08:00
licenses Alliance for Open Media: new library 2020-10-06 08:45:24 -07:00
recipes-connectivity gssdp: check opengl is enabled or not 2022-11-10 10:41:35 -08:00
recipes-dvb Make tvheadend recipe compatible with the latest tvheadend version 2023-01-12 09:02:10 -08:00
recipes-mkv meta-multimedia: Fix missing upstream status in several patches 2023-04-05 20:34:24 -07:00
recipes-multimedia x265: Pass --debug-prefix-map to nasm 2023-05-28 16:42:01 -04:00
recipes-support crossguid: Fix build with gcc13 2023-01-26 10:24:25 -08:00
COPYING.MIT meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
README meta-openemnedded: Add myself as mickledore maintainer 2023-04-09 08:52:55 -07:00

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: mickledore

URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe
branch: mickledore

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia][mickledore]' in the subject

When sending single patches, please use something like:
git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-multimedia][mickledore][PATCH'

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like GitLab, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Layer maintainer: Armin Kuster <akuster808@gmail.com>