openembedded-core.git/meta/recipes-devtools/llvm, branch thud

llvm: Enable AMDGPU backend for native/native-sdk builds too

2018-08-21T13:49:34+00:00

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

llvm: Use HOST_ARCH in LLVM_TARGETS_TO_BUILD for builds

2018-08-21T13:49:34+00:00

LLVM_TARGETS_TO_BUILD is needed to represent HOST_ARCH for
builds and target specific additions should use class-target
override

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

llvm: Use YOCTO_ALTERNATE_MULTILIB_NAME environment variable in llvm-config

2018-08-20T09:43:59+00:00

llvm-config is a tool on similar veins as pkg-config but provides a lot
more information and packages which use llvm e.g. mesa use this tool to
poke for llvm related informaiton e.g. version, libpath, includepaths
to name a few, this has few challanges in cross build environments where
llvm-config is supposed to be build for buildhost but provide information
about target llvm which is addressed by building native llvm-config along
with target llvm build, but this is frowned upon by OE build system since
it detects that host paths are being used so we have to build it as part
of llvm-native but then it means install paths for llvm and llvm-native
are different and wrong paths get reported when llvm-config is used.
This is solved by providing YOCTO_ALTERNATE_EXE_PATH variable to let
llvm-config use that path instead of self-relative path to report back

Second problem is when building multi-lib packages base_libdir is different
for target packages but native llvm-config does not know about it so
it reports non-multilibbed paths as libdir and packages can not find
llvm in sysroot. This is fixed by adding another environment variable
YOCTO_ALTERNATE_MULTILIB_NAME which can be set from recipes to set
proper multilib path

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

llvm: Point llvm-config to one built with llvm-native

2018-08-20T09:43:59+00:00

If not defined, llvm build system tries to build one
which then confuses the OE QA system since its building
native tool and target packages in same package build
moreover it is not required since we already have it via
llvm-native

Fixes
ERROR: llvm-6.0-r0 do_package_qa: QA Issue: llvm: The compile log indicates that host include and/or library paths were used.

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

llvm: Update to 6.0.1

2018-08-16T21:38:20+00:00

Drop upstreamed patch

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

llvm: Fix [compile-host-path] QA issue

2018-05-04T08:54:58+00:00

Its trying to build NATIVE llvm-config which is
already built with llvm-native so we do not need
to rebuild it

Drop setting NINJA_STATUS explicitly, its no longer
needed, on the contrary it hinders the task status
update

Signed-off-by: Khem Raj 
Signed-off-by: Ross Burton

llvm: Upgrade to 6.0 release

2018-04-05T13:49:00+00:00

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

oe-core: take UPSTREAM_CHECK_COMMITS into use where possible

2017-11-29T23:41:36+00:00

This greatly reduces the amount of recipes for which upstream
version check fails: from about 30 to about 8.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Ross Burton

llvm: Use the SRCREV past final 5.0 release

2017-11-05T13:44:54+00:00

Signed-off-by: Khem Raj 
Signed-off-by: Ross Burton

meta: drop True option to getVar calls

2017-09-25T13:18:38+00:00

Search made with the following regex: getVar ?\((.*), True\).

Signed-off-by: Ming Liu 
Signed-off-by: Richard Purdie