From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/6] package/mesa3d: enable OpenCL support
Date: Sun, 21 Oct 2018 13:10:58 +0200 [thread overview]
Message-ID: <20181021131058.56711035@windsurf> (raw)
In-Reply-To: <4f7be120-98ed-8c1c-3f01-fb35dbad27cb@gmail.com>
Hello,
On Sun, 21 Oct 2018 12:53:45 +0200, Valentin Korenblit wrote:
> > +LIBCLC_INCLUDEDIR is the location where mesa3d OpenCL implementation
> > +will look for OpenCL "headers" on the target, when building the OpenCL
> > +kernels.
>
> Maybe it is clearer to write "OpenCL library headers", so we don't get confused
> with Khronos OpenCL-Headers.
I understand the confusion, but "OpenCL library headers" actually make
me think about the Khronos headers, i.e the headers that describe the
API of the OpenCL.so library.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-21 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 22:14 [Buildroot] [PATCH 0/6] OpenCL support Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 1/6] package/opengl/opencl: new virtual package Thomas Petazzoni
2018-10-21 10:46 ` Valentin Korenblit
2018-10-21 14:29 ` Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 2/6] package/mesa3d: enable OpenCL support Thomas Petazzoni
2018-10-21 10:53 ` Valentin Korenblit
2018-10-21 11:10 ` Thomas Petazzoni [this message]
2018-10-20 22:14 ` [Buildroot] [PATCH 3/6] package/mesa3d-headers: install OpenCL headers when needed Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 4/6] package/nvidia-driver: use += where appropriate Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 5/6] package/nvidia-driver: become an OpenCL provider Thomas Petazzoni
2018-10-20 22:14 ` [Buildroot] [PATCH 6/6] package/clinfo: new package Thomas Petazzoni
2018-12-03 22:09 ` [Buildroot] [PATCH 0/6] OpenCL support Thomas Petazzoni
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=20181021131058.56711035@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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 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.