From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Gilles Talis <gilles.talis@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/opencl-clhpp: new package
Date: Wed, 27 Jul 2022 09:29:34 +0200 [thread overview]
Message-ID: <20220727092934.73f3404c@windsurf> (raw)
In-Reply-To: <20220116175320.453041-1-gilles.talis@gmail.com>
Hello Gilles,
On Sun, 16 Jan 2022 18:53:19 +0100
Gilles Talis <gilles.talis@gmail.com> wrote:
> diff --git a/package/opencl-clhpp/Config.in b/package/opencl-clhpp/Config.in
> new file mode 100644
> index 0000000000..12045be055
> --- /dev/null
> +++ b/package/opencl-clhpp/Config.in
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_OPENCL_CLHPP
> + bool "opencl-clhpp"
> + depends on BR2_INSTALL_LIBSTDCPP
I've added a dependency on BR2_PACKAGE_HAS_LIBOPENCL here. While it is
not needed for this package to build (because it now only install
headers), all users of opencl-clhpp will need to have this dependency.
> diff --git a/package/opencl-clhpp/opencl-clhpp.hash b/package/opencl-clhpp/opencl-clhpp.hash
> new file mode 100644
> index 0000000000..27b27cd80c
> --- /dev/null
> +++ b/package/opencl-clhpp/opencl-clhpp.hash
> @@ -0,0 +1,3 @@
> +# Locally Computed
> +sha256 869456032e60787eed9fceaeaf6c6cb4452bc0ff97e0f5a271510145a1c8f4d4 opencl-clhpp-2.0.16.tar.gz
> +sha256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30 LICENSE.txt
> diff --git a/package/opencl-clhpp/opencl-clhpp.mk b/package/opencl-clhpp/opencl-clhpp.mk
> new file mode 100644
> index 0000000000..610cd45b62
> --- /dev/null
> +++ b/package/opencl-clhpp/opencl-clhpp.mk
> @@ -0,0 +1,16 @@
> +################################################################################
> +#
> +# opencl-clhpp
> +#
> +################################################################################
> +
> +OPENCL_CLHPP_VERSION = 2.0.16
> +OPENCL_CLHPP_SITE = $(call github,KhronosGroup,OpenCL-CLHPP,v$(OPENCL_CLHPP_VERSION))
> +OPENCL_CLHPP_LICENSE = Apache-2.0
> +OPENCL_CLHPP_LICENSE_FILES = LICENSE.txt
> +OPENCL_CLHPP_INSTALL_STAGING = YES
> +
> +# OpenCL_CLHPP is a header-only library
> +OPENCL_CLHPP_INSTALL_TARGET = NO
> +
> +$(eval $(cmake-package))
As suggested by Romain, I have used generic-package and a simple
OPENCL_CLHPP_INSTALL_STAGING_CMDS to just install the two headers to
avoid the need for a C++11 compiler.
Applied with those changes, thanks!
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-27 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 17:53 [Buildroot] [PATCH 1/2] package/opencl-clhpp: new package Gilles Talis
2022-01-16 17:53 ` [Buildroot] [PATCH v2 2/2] package/clpeak: " Gilles Talis
2022-07-26 21:09 ` Romain Naour
2022-07-27 7:32 ` Thomas Petazzoni via buildroot
2022-07-26 20:39 ` [Buildroot] [PATCH 1/2] package/opencl-clhpp: " Romain Naour
2022-07-27 7:29 ` Thomas Petazzoni via buildroot [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=20220727092934.73f3404c@windsurf \
--to=buildroot@buildroot.org \
--cc=gilles.talis@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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