linux/poky.git/meta/classes/distutils-common-base.bbclass, branch uninative-1.9

distutils,setuptools: Delete use of SECURITY_NO_PIE_CFLAGS

2017-07-08T12:34:45+00:00

gcc can handle PIE in gcc driver (From OE-Core rev: fcfe6d4ab4460f8358e13023022a5e909941ca93) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

distutils-base.bbclass: Do not use -pie with hardening

2017-06-09T16:12:14+00:00

Fix build when PIE is turned on. It tries to build .so file using -pie and -shared flags together because its doing compile and link in same step CFLAGS and LDFLAGS are combined and does not work, ending in errors e.g. | /mnt/a/oe/build/tmp/work/cortexa7t2hf-neon-vfpv4-bec-linux-musleabi/python-pygpgme/0.3-r0/recipe-sysroot/usr/l ib/Scrt1.o: In function `_start_c': | /usr/src/debug/musl/1.1.16+gitAUTOINC+179766aa2e-r0/git/crt/crt1.c:17: undefined reference to `main' | collect2: error: ld returned 1 exit status This error while cryptic is due to the fact that we are building a shared library but also pass -pie flag to the link step after specify LDHSARED ( which is -shared linker flags ) we can not use -pie when doing shared libs. This is true for all the python modules inheriting setup tools Disable the pie flags thusly for all modules using setuptools since this setting is done in setuptools makefiles which are then used during module compiles (From OE-Core rev: 6a4e3b696d32809279f1550cc1d67bc6b9979a03) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

distutils-common-base.bbclass: remove EXTRA_OEMAKE workaround

2016-09-03T08:58:40+00:00

The default of EXTRA_OEMAKE is already empty since commit: OE-Core rev: aeb653861a0ec39ea7a014c0622980edcbf653fa bitbake.conf: Remove unhelpful default value for EXTRA_OEMAKE (From OE-Core rev: 641ab36095eb72898ec808e655014bbc5900eb95) Signed-off-by: Stefan Müller-Klieser Signed-off-by: Richard Purdie

python3-dir.bbclass: add a separate class for Python 3

2016-06-01T11:38:41+00:00

This is much cleaner than sharing python-dir.bbclass between python 2 and 3 classes, and doing confusing overrides in them. (From OE-Core rev: 3891fcec863602a0ae6d0f3d305ea50a79a205d9) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

distutils-common-base: do not set PACKAGES - use defaults from bitbake.conf

2016-01-26T22:32:00+00:00

it took me a while to understand why PACKAGE_BEFORE_PN did not work... (From OE-Core rev: 50f0a2a041df679f06c0b93a0472905e8c129bd4) Signed-off-by: Andreas Müller Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: Drop now pointless manual -dbg packaging

2015-12-16T11:56:30+00:00

With the autodebug package generation logic, specifically setting FILES_${PN}-dbg isn't needed in most cases, we can remove them. (From OE-Core rev: 3ab59d49dd7c18e194b58d1248b4b87709b5a738) Signed-off-by: Richard Purdie

distutils-common-base: add to, don't set, FILES_${PN}

2015-06-23T10:47:39+00:00

If we set FILES_${PN} and a recipe inherits other classes that modify FILES_${PN} *before* distutils-common-base is included, any changes to FILES_${PN} made by those classes are lost. Instead, append the additional directories we want to include in FILES_${PN} (From OE-Core rev: f6478e8c73f9cfb79d1f7680b7bf3ff957eb51cb) Signed-off-by: Joshua Lock Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

distutils-common-base: Create staticdev pacakge for static libraries

2012-11-21T16:56:00+00:00

(From OE-Core rev: 0c4c3ebfedd06b2b8f36747bc0c0d986f05420cf) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

distutils(-common-base) bbclass: sync with OE

2011-01-20T21:37:00+00:00

When using python recipes imported from OE (e.g. python-cheetah) parsing only succeeds when python has already been built due to the PYTHON_DIR references. This commit syncs the classes with OE to make it work, but keeps the *.pyo removal from yocto. Signed-off-by: Koen Kooi Signed-off-by: Saul Wold

distutils: Sync with OE.dev

2009-12-05T23:18:02+00:00

Signed-off-by: Richard Purdie