| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Only when CLANGSDK = 1
Fixes Issue #338
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
define CLANG_TIDY_EXE which is used by some build systems e.g. cmake
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
clang-5.0 supports the option now
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
It does not work and moreover its redundant
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These options were introduced in OE-Core to support multi libc SDKs
and added with
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Sat Jul 25 14:48:21 2015 +0100
toolchain-scripts: For non-glibc, pass compiler options to ensure the correct libc selection
gcc-cross-canadian-<arch> is only built once. It needs to target all the
different libcs, not just the currently selected one. This change ensures
that if another libc is used, the compiler correctly selects the right one.
[YOCTO #8025]
(From OE-Core rev: da2e92e256054b137a1646fdad1fe1a47ba3215a)
Clang however acts based on crosscompiler name and does not have option to controlled
multi libc scene
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>
|
