Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/build: Add BLUEZ_EXTENSIONS to default cflags
Date: Tue, 23 Sep 2014 16:13:18 +0200	[thread overview]
Message-ID: <9540580.EFTB4ij8tO@uw000953> (raw)
In-Reply-To: <1411454927-27079-1-git-send-email-jakub.tyszkowski@tieto.com>

Hi Jakub,

On Tuesday 23 of September 2014 08:48:47 Jakub Tyszkowski wrote:
> This is to be sure that all modules knows when we use extensions.
> ---
>  android/Android.mk | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/android/Android.mk b/android/Android.mk
> index db5032d..8887a97 100644
> --- a/android/Android.mk
> +++ b/android/Android.mk
> @@ -14,6 +14,10 @@ BLUEZ_COMMON_CFLAGS := -DVERSION=\"$(BLUEZ_VERSION)\" \
>  			-DANDROID_VERSION=$(ANDROID_VERSION) \
>  			-DANDROID_STORAGEDIR=\"/data/misc/bluetooth\" \
>  
> +ifeq ($(BLUEZ_EXTENSIONS), true)
> +BLUEZ_COMMON_CFLAGS += -DBLUEZ_EXTENSIONS
> +endif
> +
>  # Enable warnings enabled in autotools build
>  BLUEZ_COMMON_CFLAGS += -Wall -Wextra \
>  			-Wdeclaration-after-statement \
> @@ -142,10 +146,6 @@ LOCAL_SHARED_LIBRARIES := \
>  
>  LOCAL_CFLAGS := $(BLUEZ_COMMON_CFLAGS)
>  
> -ifeq ($(BLUEZ_EXTENSIONS), true)
> -LOCAL_CFLAGS += -DBLUEZ_EXTENSIONS
> -endif
> -
>  LOCAL_MODULE := bluetooth.default
>  LOCAL_MODULE_PATH := $(TARGET_OUT_SHARED_LIBRARIES)/hw
>  LOCAL_MODULE_TAGS := optional
> 

Patch applied. Thanks.

-- 
Best regards, 
Szymon Janc

      reply	other threads:[~2014-09-23 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  6:48 [PATCH] android/build: Add BLUEZ_EXTENSIONS to default cflags Jakub Tyszkowski
2014-09-23 14:13 ` Szymon Janc [this message]

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=9540580.EFTB4ij8tO@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=jakub.tyszkowski@tieto.com \
    --cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox