| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Used script 'scripts/contrib/convert-overrides.py' from
openembedded-core meta layer to add new override syntax
to make it work with BitBake 1.52 (Honister 3.4) or later.
Signed-off-by: Preeti Sachan <preeti.sachan@intel.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
CLANGSDK is 1
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
when clang is not default compiler
Fixes issue #63
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
build llvm libunwind along with libcxx
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
| |
This is preferred way of building libc++ and
it also means we do not need musl specific tweaks
since top level build from llvm already know
musl and make right choices
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
| |
toolchain
Applying the below patch gets rid of all of the extra packages except
glibmm-dev. I have no idea where that is coming from!
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
package libcxxabi-dev and compiler-rt-staticdev
into packagegroup-core-standalone-sdk-target so it
gets into SDK
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
ALLOW_EMPTY is added so packaging can succeed
the files are all static libs
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Also export CLANGCC, CLANGCXX, CLANGCPP in SDK environment which can
then be used to compile applications in SDK
Additionally remove -mthumb-interwork from compiler options if target is
arm
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|