| Age | Commit message (Collapse) | Author |
|---|
|
Add aarch64 as a valid machine to cpuburn recipe and split compilation
task.
The only source file which supports the aarch64 build is cpuburn-a53.S,
and in case if TUNE is set to aarch64 - this should be the only file to
be assembled to the application.
In case of 32-bit build - all sources are compiled as they are, since
cpuburn-a53.S supports both 32- and 64-bit tunes.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
This provides more benchmarks for different arm arches >= v7
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
Previous location is no longer accessible and breaks builds that include
cpuburn-neon. This updates the location to fix the build breaks
Signed-off-by: Lauren Post <lauren.post@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Changes:
- rename SUMMARY with length > 80 to DESCRIPTION
- rename DESCRIPTION with length < 80 to (non present tag) SUMMARY
- drop final point character at the end of SUMMARY string
- remove trailing whitespace of SUMMARY line
Note: don't bump PR
Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* 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>
|
|
* The package were not versioning the sources as the files had no
version on its name. We workaround it mangling the DL_DIR;
* We now dynamically check if the machine has or not neon feature and
set COMPATIBLE_MACHINE.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
Andrey Zhizhikin
Fabio Berton
Khem Raj
Lauren Post
Matthieu CRAPET
Martin Jansa
Otavio Salvador
Koen Kooi