summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/libcap/libcap_2.24.bb
Commit message (Collapse)AuthorAgeFilesLines
* meta: rename perl-native-runtimeEd Bartosh2016-01-111-1/+1
| | | | | | | | | | | | | | | | The code in native.bbclass adds -native suffix to the package names that don't have it. perl-native-runtime becomes perl-native-runtime-native because of this. Renamed perl-native-runtime -> hostperl-runtime-native to avoid mangling it and to conform with the naming convetion for native packages. (From OE-Core rev: f4dade8e765a8c7bfd131728b9e0a34631e24950) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: Drop now pointless manual -dbg packagingRichard Purdie2015-12-161-1/+0
| | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* libcap: control attr PACKAGECONFIG via xattr DISTRO featureAndre McCurdy2015-07-201-1/+2
| | | | | | | | (From OE-Core rev: 67a588a11998068b3a7dd38d46382d0c2990ea93) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcap: avoid losing default Large File Support CFLAGSAndre McCurdy2015-07-201-0/+3
| | | | | | | | | | | | -D_LARGEFILE64_SOURCE and -D_FILE_OFFSET_BITS=64 are present in the default libcap CFLAGS. Add them to the OE CFLAGS too, so that they are still in effect when the OE CFLAGS over-ride the defaults. (From OE-Core rev: 974c8266b30ae114ab331f0ce39fd0fcf4868f1a) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcap: always link apps dynamicallyAndre McCurdy2015-07-201-0/+1
| | | | | | | | | | | Without the explicit over-ride, apps will be linked statically if a .git directory is found in the top level source directory. (From OE-Core rev: aa6f5da8d42deb3d3b98209dc716b5a116d22d48) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcap: Avoid passing "-e" to makeMike Crowe2015-05-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | oe-core 51540b64f62234c145fc32cfa3fbbaaebbeece08 altered libcap.inc (at the time) to append to EXTRA_OEMAKE rather than assign to it. The default value for EXTRA_OEMAKE contains "-e". This means that the change caused "-e" to be passed to make for the first time. Unfortunately passing "-e" subtly changes the behaviour of libcap's Make.Rules under recursive make when prefix="" (which it is for us since we're using meta-micro.) Without "-e" the prefix comes from the command line in both the parent and submakes. This takes precedence over any attempt to reassign it with a simple "=" operation so the headers are correctly installed in (empty string)/include. With "-e" the prefix still comes from the command line in the parent make but from the environment in the submake. The attempt to assign it fails in the parent make as before, but not in the submake so the headers are installed incorrectly in /usr/include. In all four cases the "ifdef prefix" else clause is executed. So, let's assign EXTRA_OEMAKE in order to avoid using "-e" at all. (From OE-Core rev: a8d35fa4fd76ea4a70063492cd5eab0858f2edb6) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcap: Upgrade to 2.24Saul Wold2014-11-091-0/+72
Tarballs moved to kernel.org Deleted upstream'ed patch merged minimal .bb with .inc Check for security dir before moving it when pam is enabled. (From OE-Core rev: 73f2b69b17e5364388faf0f31275c3c69fb31030) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>