gnome-bluetooth needs libcanberra compiled with gtk+3 support, compiling
libcanberra with gtk+3 support would need gtk+ which needs X11 to
support the needed backend, other option is directfb which will not
worrk work with wayland(without X) config either
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ver 3.34.1:
- Prefer “Alias†adapter name to “Nameâ€
- Fix some memory leaks
- Updated translations
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is the latest upstream stable version.
Besides simple version bump this patch also makes the following changes:
1. Switch build system from autotools to meson.
2. Drop x11 as required distro feature. This package by itself does not
depend on x11. It's perfectly usable in headles or wayland only
environments.
3. Drop intltool-native and gnome-common-native from DEPENDS since those
packages no longer seem to be needed by meson based build setup.
4. Add runtime dependency on bluez5. The package obviously needs it to
function, but since it does not link with any libs provided by bluez5
(it talks to bluez stack via dbus) this dependency won't be added
automatically.
5. Inherit upstream-version-is-even since GNOME packages do follow
versioning convention checked by this bbclass.
Signed-off-by: Piotr Tworek <tworaz@tworaz.net>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
gnome-common is deprecated and gnomebase.bbclass will soon stop depending on it,
so add gnome-common to DEPENDS for the recipes that still use it.
gxim previously wasn't really using the gnome-common macros so now the build
fails with compiler errors, so pass the flag to turn off fatal warnings as gxim
appears to be dead.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
bluez4 is removed from oe-core
This helps in compiling them when distro features are either set to use
bluez4 or bluez5
Signed-off-by: Khem Raj <raj.khem@gmail.com>
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>
Fix errors like below
| bluetooth-input.c:193:4: error: format '%d' expects argument of type
'int', but argument 5 has type 'XID' [-Werror=format=]
| g_message ("has mouse: %s (id = %d)", device_info[i].name,
device_info[i].id);
| ^
| bluetooth-input.c:198:4: error: format '%d' expects argument of type
'int', but argument 5 has type 'XID' [-Werror=format=]
| g_message ("has keyboard: %s (id = %d)", device_info[i].name,
device_info[i].id);
| ^
Signed-off-by: Khem Raj <raj.khem@gmail.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>
