| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
License files changes:
+ * This file was part of the Independent JPEG Group's software:
* Copyright (C) 1991-1998, Thomas G. Lane.
* Modified 2002-2009 by Guido Vollbeding.
- * Copyright (C) 2009-2011, D. R. Commander.
- * This file is part of the Independent JPEG Group's software.
+ * Modifications:
+ * Copyright (C) 2009-2011, 2013, D. R. Commander.
Update SRC_URI to match new SF layout.
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
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>
|
| |
|
|
|
|
|
|
| |
This fixes "ERROR: Multiple .bb files are due to be built which each provide jpeg"
Signed-off-by: Samuel Stirtzel <s.stirtzel@googlemail.com>
Acked-by: Chase Maupin <chase.maupin@ti.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with SIMD support
* configure checks that the same as in native case
| configure:13139: checking if we have SIMD optimisations for cpu type
| configure:13143: result: yes (x86_64)
| configure:13151: checking for nasm
| configure:13181: result: no
| configure:13151: checking for nasmw
| configure:13181: result: no
| configure:13151: checking for yasm
| configure:13181: result: no
| configure:13189: error: no nasm (Netwide Assembler) found
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
| |
|
|
|
| |
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
Acked-by: Martin Jansa <Martin.Jansa@gmail.com>
|
| |
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
| |
|
|
|
|
|
|
| |
without following oe-core's version PREFERRED_PROVIDER_jpeg does not work and
libjpeg is build.
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
| |
|
|
|
|
|
|
| |
* We have various variables which are either not quoted at all or are
* half quoted. This patch fixes the bad exmaples so everything is consistent.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
| |
|
|
|
|
|
|
| |
else I get the following error during configure :
| configure: error: no nasm (Netwide Assembler) found
Signed-off-by: Eric Bénard <eric@eukrea.com>
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
|
|
If you're on x86 or ARM this will be a lot faster due to SIMD optimizations
Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
|
