Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] bluez5_utils-headers: new package
Date: Mon, 10 Sep 2018 17:56:53 +0200	[thread overview]
Message-ID: <20180910155653.GE2674@scaer> (raw)
In-Reply-To: <20180905113931.6703-1-grzegorz@blach.pl>

Grzegorz, All,

On 2018-09-05 13:39 +0200, Grzegorz Blach spake thusly:
> Header files from bluez utils version 5.x.
> 
> Separated headers are required to break circular dependencies
> when python3 is build with bluetooth support.
> 
> Signed-off-by: Grzegorz Blach <grzegorz@blach.pl>
> ---
[--SNIP--]
> diff --git a/package/bluez5_utils-headers/bluez5_utils_headers.hash b/package/bluez5_utils-headers/bluez5_utils_headers.hash
> new file mode 100644
> index 0000000000..b965708559
> --- /dev/null
> +++ b/package/bluez5_utils-headers/bluez5_utils_headers.hash
> @@ -0,0 +1,4 @@
> +# From https://www.kernel.org/pub/linux/bluetooth/sha256sums.asc:
> +sha256  5ffcaae18bbb6155f1591be8c24898dc12f062075a40b538b745bfd477481911  bluez-5.50.tar.xz
> +sha256  b499eddebda05a8859e32b820a64577d91f1de2b52efa2a1575a2cb4000bc259  COPYING
> +sha256  ec60b993835e2c6b79e6d9226345f4e614e686eb57dc13b6420c15a33a8996e5  COPYING.LIB
> diff --git a/package/bluez5_utils-headers/bluez5_utils_headers.mk b/package/bluez5_utils-headers/bluez5_utils_headers.mk
> new file mode 100644
> index 0000000000..9bc463432c
> --- /dev/null
> +++ b/package/bluez5_utils-headers/bluez5_utils_headers.mk
> @@ -0,0 +1,21 @@
> +################################################################################
> +#
> +# bluez5_utils-headers
> +#
> +################################################################################
> +
> +BLUEZ5_UTILS_HEADERS_VERSION = 5.50
> +BLUEZ5_UTILS_HEADERS_SOURCE = bluez-$(BLUEZ5_UTILS_VERSION).tar.xz

Since we are using the same source tarball as for bluez5_utils, we want
to download it and store it only once:

    BLUEZ5_UTILS_HEADERS_DL_SUBDIR = bluez5_utils

Consequently, the hash file should be a symlink to the one from
bluez5_utils.

See for example mesa3d and mesa3d-headers for an example.

Regards,
Yann E. MORIN.

> +BLUEZ5_UTILS_HEADERS_SITE = $(BR2_KERNEL_MIRROR)/linux/bluetooth
> +BLUEZ5_UTILS_HEADERS_LICENSE = GPL-2.0+, LGPL-2.1+
> +BLUEZ5_UTILS_HEADERS_LICENSE_FILES = COPYING COPYING.LIB
> +
> +BLUEZ5_UTILS_HEADERS_INSTALL_STAGING = YES
> +BLUEZ5_UTILS_HEADERS_INSTALL_TARGET = NO
> +
> +define BLUEZ5_UTILS_HEADERS_INSTALL_STAGING_CMDS
> +	$(INSTALL) -d $(STAGING_DIR)/usr/include/bluetooth/
> +	$(INSTALL) -m 644 $(@D)/lib/*.h $(STAGING_DIR)/usr/include/bluetooth/
> +endef
> +
> +$(eval $(generic-package))
> -- 
> 2.17.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2018-09-10 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 11:39 [Buildroot] [PATCH 1/2] bluez5_utils-headers: new package Grzegorz Blach
2018-09-05 11:39 ` [Buildroot] [PATCH 2/2] python3: add optional dependency on bluez5_utils-headers Grzegorz Blach
2018-09-10 15:56 ` Yann E. MORIN [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-13 11:56 [Buildroot] [PATCH 1/2] bluez5_utils-headers: new package Grzegorz Blach
     [not found] ` <20180915000534.210ed343@windsurf>
2018-09-17 12:14   ` Grzegorz Blach
2018-10-21 15:44     ` Arnout Vandecappelle

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=20180910155653.GE2674@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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