On 04/02/2015 07:10 PM, Burton, Ross wrote:
On 2 April 2015 at 04:24, Robert Yang mailto:liezhi.y...@windriver.com>> wrote:
I'm afraid not since it depends on virtual/libx11.
So what's gained by disabling freeglut? Shouldn't we be enabling it if possible?
There is no freeglut in oe-co
Signed-off-by: Andre McCurdy
---
meta/recipes-support/libevent/libevent_2.0.21.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-support/libevent/libevent_2.0.21.bb
b/meta/recipes-support/libevent/libevent_2.0.21.bb
index 1230e92..e198f09 100644
--- a/meta/rec
Signed-off-by: Andre McCurdy
---
.../libevent/libevent-2.0.21/disable_tests.patch | 15 ---
.../libevent-2.0.21/obsolete_automake_macros.patch| 15 ---
.../libevent/{libevent_2.0.21.bb => libevent_2.0.22.bb} | 11 +++
3 files changed, 3 insertion
The logic tries to remove the -native suffix from pn to handle this (though it
doesn't succeed, as it doesn't assign the new pn to the variable), but we need
to do more for the swspec tasks than just not set the extrapath, we also need
to change from SSTATE_PKGSPEC to SSTATE_SWSPEC. Alter to correc
On 03/04/2015 15:13, Cristian Iorga wrote:
- Large release with over a month and 475 commits since 5.28;
- Internal GATT library received lots of updates;
- Fix for AVCTP key repeat timeout;
- Added support for the Multi Profile Specification (MPS).
Signed-off-by: Cristian Iorga
---
meta/reci
On Fri, Apr 3, 2015 at 11:34 AM, Jun Zhu wrote:
> oe.utils.both_contain() should return the result as "checkvalue" or "",
> but the latest implement returns as "set(['checkvalue'])" or "";
>
> It causes that bitbake.conf generates the wrong result of COMBINED_FEATURES,
> which contains the common
From: "Krishnanjanappa, Jagadeesh"
Building both 32-bit and 64-bit binaries in valgrind at a time would
lead to following QA issue as below,
(snip)
ERROR: QA Issue: Architecture did not match (62 to 3) on
${WORKDIR}/valgrind/3.10.1-r0/packages-split/valgrind-dbg/usr/lib64/valgrind/.debug/vgpr
>With a multilib configuration, these things should be packaged per-multilib and
>then only the installed multilib components are available on the device. It
>saves space and preserves the checking in place to catch situations where you
>may accidentally provide software that isn't runnable.
>The
On 4/3/15 9:57 AM, Krishnanjanappa, Jagadeesh wrote:
>> what is the point of packaging files for which there won’t be any runtime
>> >environment. You are just better of removing them.
>> IMO unless you have multilib environment working
>> this patch is just relaxing the QA
>
> With compilers sup
> what is the point of packaging files for which there won’t be any runtime
> >environment. You are just better of removing them.
>IMO unless you have multilib environment working
>this patch is just relaxing the QA
With compilers supporting generation of multilib and yocto framework supporting
Morning all,
I am trying to replicate how Poky is created using combo-layer. I have
referenced https://wiki.yoctoproject.org/wiki/Combo-layer
The issue seems to be related when I define "branch". Not defining it
works fine (ie, master default). I suspect I am doing something
incorrectly or
- Large release with over a month and 475 commits since 5.28;
- Internal GATT library received lots of updates;
- Fix for AVCTP key repeat timeout;
- Added support for the Multi Profile Specification (MPS).
Signed-off-by: Cristian Iorga
---
meta/recipes-connectivity/bluez5/{bluez5_5.28.bb => blu
For a distro that contains bluetooth feature, set bluez5
as the default Bluetooth stack, while still allowing the
use of bluez4 as an alternative Bluetooth stack.
Signed-off-by: Cristian Iorga
---
meta/classes/bluetooth.bbclass | 16 +++-
1 file changed, 11 insertions(+), 5 deletions
BlueZ 4.x and associated recipes are now obsolete
(bluez4, bluez-hcidump, gst-plugin-bluetooth).
Will be moved into networking collection of meta-oe.
BlueZ 4.x is still usable in oe-core as alternative Bluetooth stack.
Signed-off-by: Cristian Iorga
---
.../obsolete_automake_macros.patch
info updated accordingly.
Signed-off-by: Cristian Iorga
---
meta-yocto/conf/distro/include/upstream_tracking.inc | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta-yocto/conf/distro/include/upstream_tracking.inc
b/meta-yocto/conf/distro/include/upstream_tracking.inc
index 15f6a18..2c6a074
bluez4, bluez-hcidump, gst-plugin-bluetooth recipes
will be removed from oe-core, maintainers removed.
Signed-off-by: Cristian Iorga
---
meta-yocto/conf/distro/include/maintainers.inc | 3 ---
1 file changed, 3 deletions(-)
diff --git a/meta-yocto/conf/distro/include/maintainers.inc
b/meta-yoc
BlueZ 5.x is now the default Bluetooth stack.
BlueZ 4.x is moved to meta-oe networking collection
and still supported in oe-core.
The following changes since commit d6d2dd5c9e06c54ff336b44d54f01b4fe24903ed:
tools: A real fix for thos mega-manual.sed file for Toaster. (2015-04-02
20:30:46 +0100
oe.utils.both_contain() should return the result as "checkvalue" or "",
but the latest implement returns as "set(['checkvalue'])" or "";
It causes that bitbake.conf generates the wrong result of COMBINED_FEATURES,
which contains the common components in both DISTRO_FEATURE and
MACHINE_FEATURES.
18 matches
Mail list logo
