All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Daniel Ache <daniel.k.ache@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: meta-qt5 bluetooth not working within qtconnectivity
Date: Thu, 24 Sep 2015 08:18:20 +0200	[thread overview]
Message-ID: <20150924061820.GC2404@jama> (raw)
In-Reply-To: <CAP8S4ik4+rWgJL-4RFj8c-bfW6XohBr+QokXFj6k52SYGMHuHQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3422 bytes --]

On Thu, Sep 24, 2015 at 08:05:58AM +0200, Daniel Ache wrote:
> Dear Martin,

Hi,

please use ML openembedded-devel@lists.openembedded.org for generic
questions like this.

> 
> We are not so used to Yocto, so we had to patch meta-qt5 (
> qtconnectivity_git.bb and qtsystems_git.bb) to compile bluetooth. bluez4 is
> a used package within our recipe but bluetooth is not included without this
> patch :-(
> 
> Is "OE_BLUEZ_ENABLED" needed somehow? Or is this historical stuff?

Yes, it's still needed, but don't set it directly add "bluez4" to
PACKAGECONFIG variable in your DISTRO config.

> How can I change our recipes to compile with bluetooth and without patching
> meta-qt5?

Use .bbappend or PACKAGECONFIG_append_pn-qtconnectivity.

Did you test it with bluez5 or only with bluez4? I didn't check if 5.5
version supports both now.

Regards,

> Attached out patch file, so you can see what we did.
> 
> greetings from Germany
> Daniel

> From eb16df8826aeca2eab878695e8d2645a191e717c Mon Sep 17 00:00:00 2001
> From: Daniel Ache <d.ache@oculus.de>
> Date: Wed, 23 Sep 2015 16:23:25 +0200
> Subject: [PATCH 1/1] =?UTF-8?q?OE=5FBLUEZ=5FENABLED=20entfernt.=20Da=20wir?=
>  =?UTF-8?q?=20(Christian=20Wa=C3=9Fmuth=20und=20ich)=20es=20nicht=20gescha?=
>  =?UTF-8?q?fft=20haben,=20QtConnectivity=20so=20mit=20bluez=20support=20zu?=
>  =?UTF-8?q?=20erstellen.=20Vermutlich=20ist=20OE=5FBLUEZ=5FENABLED=20eh=20?=
>  =?UTF-8?q?ein=20Relikt=20aus=20vergangenen=20Tagen=20und=20so=20nicht=20m?=
>  =?UTF-8?q?ehr=20n=C3=B6tig.?=
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> ---
>  recipes-qt/qt5/qtconnectivity_git.bb | 8 --------
>  recipes-qt/qt5/qtsystems_git.bb      | 9 ---------
>  2 files changed, 17 deletions(-)
> 
> diff --git a/recipes-qt/qt5/qtconnectivity_git.bb b/recipes-qt/qt5/qtconnectivity_git.bb
> index 4781be1..c6e56ed 100644
> --- a/recipes-qt/qt5/qtconnectivity_git.bb
> +++ b/recipes-qt/qt5/qtconnectivity_git.bb
> @@ -12,13 +12,5 @@ LIC_FILES_CHKSUM = " \
>  
>  DEPENDS += "qtbase qtdeclarative"
>  
> -PACKAGECONFIG ??= ""
> -PACKAGECONFIG[bluez4] = "OE_BLUEZ_ENABLED,,bluez4"
> -
> -do_configure_prepend() {
> -    export QMAKE_CACHE_EVAL="CONFIG+=${EXTRA_OECONF}"
> -    # disable bluez test if it isn't enabled by PACKAGECONFIG
> -    sed -i 's/^qtCompileTest(bluez)/OE_BLUEZ_ENABLED:qtCompileTest(bluez)/g' ${S}/qtconnectivity.pro
> -}
>  
>  SRCREV = "e4a5dc7dbe62c32032e5e683ac1fdb57663a14b3"
> diff --git a/recipes-qt/qt5/qtsystems_git.bb b/recipes-qt/qt5/qtsystems_git.bb
> index 781cd38..47ec34d 100644
> --- a/recipes-qt/qt5/qtsystems_git.bb
> +++ b/recipes-qt/qt5/qtsystems_git.bb
> @@ -11,15 +11,6 @@ LIC_FILES_CHKSUM = " \
>  
>  DEPENDS += "qtbase qtdeclarative udev gconf"
>  
> -PACKAGECONFIG ??= ""
> -PACKAGECONFIG[bluez4] = "OE_BLUEZ_ENABLED,,bluez4"
> -
> -do_configure_prepend() {
> -    export QMAKE_CACHE_EVAL="CONFIG+=${EXTRA_OECONF}"
> -    # disable bluez test if it isn't enabled by PACKAGECONFIG
> -    sed -i 's/^    qtCompileTest(bluez)/    OE_BLUEZ_ENABLED:qtCompileTest(bluez)/g' ${S}/qtsystems.pro
> -}
> -
>  do_install_append() {
>      # Remove example.pro file as it is useless
>      rm -f ${D}${OE_QMAKE_PATH_EXAMPLES}/examples.pro	
> -- 
> 1.9.1
> 


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

           reply	other threads:[~2015-09-24  6:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAP8S4ik4+rWgJL-4RFj8c-bfW6XohBr+QokXFj6k52SYGMHuHQ@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150924061820.GC2404@jama \
    --to=martin.jansa@gmail.com \
    --cc=daniel.k.ache@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.