On Wed, Apr 30, 2014 at 05:40:53PM -0300, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador
This should include required bitbake version bump.
> ---
> meta/recipes-multimedia/alsa/alsa-tools_1.0.27.bb | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/reci
Hi all,
I'm giving the archiver class a try, following the instructions in the Yocto
Project Development manual (section 5.20.1) and the comments in
oe-core/meta/conf/local.conf.sample.extended. I'm seeing a few things which
aren't really working how I would expect. I've not dug into the source of
Signed-off-by: Otavio Salvador
---
meta/recipes-multimedia/alsa/alsa-tools_1.0.27.bb | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-multimedia/alsa/alsa-tools_1.0.27.bb
b/meta/recipes-multimedia/alsa/alsa-tools_1.0.27.bb
index dfa9b97..3113481 100644
--- a/
On 30 April 2014 16:54, Richard Purdie
wrote:
> On Tue, 2014-04-29 at 08:22 +0200, Mirza Krak wrote:
>> Hi.
>>
>> I recently updated my Ubuntu PC to 14.04 LTS which broke yocto builds.
>>
>> From what I can see is that there seems to be an issue with the tar
>> command and quilt-native recipe. B
> Khem sent couple of patches for B!=S issues, bit thanks to him!
>
> I have local patch to set B=S/autotools-brokensep for remaining failing
> recipes, but I'll wait a bit more for people to send fixes.
This patch was included in this build, that's why there is only few
issues, next build will i
On Wed, 2014-04-30 at 15:01 +0200, Radek Dostal wrote:
> Currently sed command touches every single *.py file. This modifies the
> timestamp of the file. All *.pyo files will be recompiled during the first
> boot, because timestamp will not match. This should be only necessary if
> sed command chan
On Tue, 2014-04-29 at 08:22 +0200, Mirza Krak wrote:
> Hi.
>
> I recently updated my Ubuntu PC to 14.04 LTS which broke yocto builds.
>
> From what I can see is that there seems to be an issue with the tar
> command and quilt-native recipe. But I am to newb to fix this. Do you
> guys have any i
Make sure you merge "wpa-supplicant: add libgcrypt as a dependencie"
and "nettle: add nettle to poky" before you test the new version of
gnutls.
The following changes since commit 17daa2ba6280304771c5fe52b94eb56f0c087490:
bitbake: bb.utils, bb.codeparser: Add bb.utils.contains_any (2014-04-29
Removes not needed or already merged patches.
Removes unused configure flags.
Tells gnutls to use the included libopts.
Removes libextra (not needed since 3.0.5).
Signed-off-by: Valentin Popa
---
meta/recipes-support/gnutls/gnutls.inc | 28 +-
.../gnutls/gnutls/25_updatedgdocfromm
Newer versions of gnutls depends on nettle.
Signed-off-by: Valentin Popa
---
meta/recipes-support/nettle/nettle_2.7.1.bb | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 meta/recipes-support/nettle/nettle_2.7.1.bb
diff --git a/meta/recipes-support/nettle/nettle_
gnutls doesn't depend on libgcrypt anymore but
wpa-supplicant does. So add it as a dependencie.
Signed-off-by: Valentin Popa
---
meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-connectivity/wpa-supplican
Currently sed command touches every single *.py file. This modifies the
timestamp of the file. All *.pyo files will be recompiled during the first
boot, because timestamp will not match. This should be only necessary if
sed command changes the file.
Signed-off-by: Radek Dostal
---
meta/classes/d
The following changes since commit 1e1b42f687b5cd34623fe2682218958e1947eb92:
feature-arm-thumb.inc: set ARMPKGSFX_THUMB only when thumb is in
TUNE_FEATURES (2014-04-29 23:35:53 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/sqlite-v
Regardless of the numbering used in source archive filenames, the
upstream version number is in dotted form in documentation, release
notes and the website, so we need to be using that here since that is
what people will expect to see.
Signed-off-by: Paul Eggleton
---
.../recipes-support/sqlite/
These add functionality required to deploy images and run tests on a
wider range of real hardware, as well as improving robustness in a
couple of areas.
A related patchset to add testing for two of the Yocto Project reference
platforms (beaglebone and edgerouter) will be sent for meta-yocto-bsp.
From: Stefan Stanacar
Right now GummibootTarget is the only hardware TEST_TARGET with deployment,
but we will add more, so let's make an abstract base class, that will
do the common thing for all the hw targets.
Signed-off-by: Stefan Stanacar
Signed-off-by: Paul Eggleton
---
meta/lib/oeqa/con
From: Stefan Stanacar
And drop the un-needed and un-used restart methods.
Only qemu ever used this and actually does it safely.
Signed-off-by: Stefan Stanacar
---
meta/lib/oeqa/controllers/masterimage.py | 3 ---
meta/lib/oeqa/targetcontrol.py | 7 ++-
2 files changed, 2 insertio
From: Stefan Stanacar
Similar to power control command, this depends on a user's setup to get to
the serial port of a board. For a local connected board this could just be:
TEST_SERIALCONTROL_CMD = "picocom /dev/ttyUSB0 -b 115200"
and for a serial console server: "telnet 10.11.12.13 7003" or so
Instead of powering up the target when the object is constructed, wait
until deploy is called. Then there are basically two different
scenarios:
a) The device is booted into the master image already, in which case
we can just use it
b) The device is booted into another image or can't be contact
If we couldn't start the target, it doesn't make sense to try and stop
it here since logically it shouldn't now be in any kind of "started"
state. (It's the start function's job to clean up after itself if it
fails - to that end, fix up the QemuTarget class so that it does.)
Signed-off-by: Paul Eg
When running automated tests (or just generally interacting with)
boards whose serial console devices are on the board itself and thus
disappear when powered down or practically disconnected, such as the
BeagleBone white, some terminal programs (e.g. picocom) will exit when
the device disappears an
If you want to do automated hardware testing but don't have a
controllable power strip this script can be useful so that you know when
you need to cycle the power.
Signed-off-by: Paul Eggleton
---
scripts/contrib/dialog-power-control | 53
1 file changed, 53
For use outside of tests themselves, we want a better error than
AssertionError, so create one and allow us to request it when calling
runCmd(). This enables us to avoid tracebacks during master image
operations if the power control command fails.
Signed-off-by: Paul Eggleton
---
meta/lib/oeqa/c
Ping
> -Original Message-
> From: Alexandru-Cezar Sardan [mailto:alexandru.sar...@freescale.com]
> Sent: Wednesday, April 09, 2014 6:01 PM
> To: openembedded-core@lists.openembedded.org
> Cc: Saul Wold; Sardan Alexandru Cezar-B41700
> Subject: [PATCH] libgcc: Use TARGET_VENDOR_virtclass-m
In the move from meta-oe to OE-core XDG based launched was dropped
without noting it in the commit message, so fix that regression.
Gnome-session will now launch the calibrator again.
Signed-off-by: Koen Kooi
---
meta/recipes-graphics/xinput-calibrator/xinput-calibrator_git.bb | 4
1 file
Op 30 apr. 2014, om 01:04 heeft Saul Wold het volgende
geschreven:
> On 04/28/2014 10:37 PM, Koen Kooi wrote:
>> In the move from meta-oe to OE-core XDG based launched was dropped
>> without noting it in the commit message, so fix that regression.
>>
>> Gnome-session will now launch the calibr
26 matches
Mail list logo
