linux/meta-clang.git/recipes-core/packagegroups, branch hardknottMirror of github.com/kraj/meta-clang.githttps://git.enea.com/cgit/linux/meta-clang.git/atom?h=hardknott2021-02-14T08:10:36+00:00packagegroup-core-buildessential: Append clang instead of overwrite2021-02-14T08:10:36+00:00Khem Rajraj.khem@gmail.com2021-02-12T08:09:37+00:00urn:sha1:e1665fee69c3c55e8614e1c9e4167d69f0bc35d1
This ensures that all buildessentials are also installed into images
which are needed when building on device
Signed-off-by: Khem Raj <raj.khem@gmail.com>
packagegroup-cross-canadian: Fix adding clang-cross-canadian only when CLANGSDK is 12020-10-20T16:21:09+00:00Khem Rajraj.khem@gmail.com2020-10-20T01:45:55+00:00urn:sha1:a405b2ed31e978b20326789007994a52d95527ee
Signed-off-by: Khem Raj <raj.khem@gmail.com>
packagegroup-core-buildessential: Add clang to rdepends2020-10-08T19:23:54+00:00Khem Rajraj.khem@gmail.com2020-10-05T17:01:25+00:00urn:sha1:43037749c750e5a976890309d04f58ef8479d4b3
This helps in ensuring that clang shows up in rootfs when tools-sdk is
selected via IMAGE_FEATURES and default TOOLCHAIN is set to be clang
Signed-off-by: Khem Raj <raj.khem@gmail.com>
packagegroup: be lenient about CLANGSDK setting2019-12-02T16:55:03+00:00Ross Burtonross.burton@intel.com2019-12-02T14:32:42+00:00urn:sha1:fabbdc8b851009163d33c8b64d0251a8cc88e71e
As CLANGSDK defaults to '1', users who have not read the README may
think that setting it to '0' would disable adding Clang to the SDK.
Little do they know that you need to *unset* the value for this to work
(as bool('0') -> True).
Change the logic to use bb.utils.contains(), so that '0' is not true.
Signed-off-by: Ross Burton <ross.burton@intel.com>
clang: Add variable CLANGSDK to control including clang in SDK2019-09-26T01:00:05+00:00Khem Rajraj.khem@gmail.com2019-09-25T21:31:10+00:00urn:sha1:ccfdb47cc4991a393a2d2fefe8420bdef56e7318
CLANGSDK ?= "1"
is default which means clang will be included into SDK
if one is using clang only for full build and dont intend to distribute
it as cross compiler SDK then set
CLANGSDK = ""
in local.conf or in another config metadata file
Signed-off-by: Khem Raj <raj.khem@gmail.com>
clang,nativesdk-packagegroup-sdk-host: Recognise risc-v2018-12-28T02:35:35+00:00Khem Rajraj.khem@gmail.com2018-12-28T02:35:35+00:00urn:sha1:79b3bc561aadb2165dd9b48314a713dc1cf9eb5f
This helps build SDKs for risc-v when meta-clang is in layer mix
even though clang for risc-v may not fully work yet
Signed-off-by: Khem Raj <raj.khem@gmail.com>
packagegroup-core-standalone-sdk-target: Make clang runtime as RRECOMMENDS2018-09-09T14:59:31+00:00Khem Rajraj.khem@gmail.com2018-08-29T19:26:31+00:00urn:sha1:7275ecf5de4b538080a846b5e415525e2f65507c
As suggested in Issue #23
this will make sure we can override it with BAD_RECOMMENDATIONS
Signed-off-by: Khem Raj <raj.khem@gmail.com>
packagegroup: Consider the fact that clang is not there for riscv64 yet2018-09-09T14:59:31+00:00Khem Rajraj.khem@gmail.com2018-08-29T19:08:08+00:00urn:sha1:a4dcd3012d5702f18cc13c33b3e5213648dc1043
Signed-off-by: Khem Raj <raj.khem@gmail.com>
packagegroup-core-standalone-sdk-target: Include libcxx and compiler-rt even when clang is not default compiler2018-07-08T22:40:38+00:00Khem Rajraj.khem@gmail.com2018-07-08T22:40:38+00:00urn:sha1:99aba60e67fdeb939367fe0c0ef098fed0d77f99
Fixes issue #63
Signed-off-by: Khem Raj <raj.khem@gmail.com>
packagegroup-core-standalone-sdk-target: Fix a typo in packagename2017-08-08T20:44:32+00:00Khem Rajraj.khem@gmail.com2017-08-08T20:44:32+00:00urn:sha1:a890c57814c5f281177899b40f0dfb760bc15f01
Signed-off-by: Khem Raj <raj.khem@gmail.com>