| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The recipe being bbappended is not supported in meta-qt6 until later in a
stable versions life cycle. This has the effect that in the most recent
version branches (6.10 as of this commit) does not have the required recipe
to bbappend, and dev will never have the recipe. This causes a parsing
error when using these more up to date branches:
ERROR: No recipes in default available for:
.../meta-clang/dynamic-layers/qt6-layer/recipes-qt/qt6/python3-pyside6_%.bbappend
Given this, we should drop this bbappend and try to address the build
failure in world another way.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
|
|
|
|
|
|
|
| |
This was setting lld as linker when using clang, but this is now
taken care by main qtbase recipe in meta-qt6. Its not needed anymore
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
it does not compile for arm64/riscv64
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
| |
This makes the chromium build less confused when mixing
native compiler for gcc and target compiler for clang
this does not sit well with gn build system and it starts
to pass clang options to gcc, which does not always work
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
chromium has certain options e.g. -Wl,-mllvm,xxx
assumed when compiler chosen is clang. These options
are not understood by GNU linker, therefore force
using LLD when clang toolchain is used to compile
QT6 components.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
| |
clang dependency is already added in meta-qt6 recipe.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
|
|
See [1]
[1] https://codereview.qt-project.org/c/yocto/meta-qt6/+/476890
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|