| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
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>
|
|
|
|
| |
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>
|