mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-01-01 13:58:06 +00:00
a45830a39b
* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Acked-by: Koen Kooi <koen@dominion.thruhere.net>
19 lines
516 B
Plaintext
19 lines
516 B
Plaintext
# Vala has problems with multiple concurrent invocations
|
|
PARALLEL_MAKE = ""
|
|
|
|
# Vala needs vala-native
|
|
DEPENDS += "vala-native"
|
|
DEPENDS_virtclass-native += "vala-native"
|
|
|
|
# Our patched version of Vala looks in STAGING_DATADIR for .vapi files
|
|
export STAGING_DATADIR
|
|
# Upstream Vala >= 0.11 looks in XDG_DATA_DIRS for .vapi files
|
|
export XDG_DATA_DIRS = "${STAGING_DATADIR}"
|
|
|
|
# Package additional files
|
|
FILES_${PN}-dev += "\
|
|
${datadir}/vala/vapi/*.vapi \
|
|
${datadir}/vala/vapi/*.deps \
|
|
${datadir}/gir-1.0 \
|
|
"
|