<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p></p>
<div class="markdown-here-wrapper" data-md-url="Thunderbird"
style="">
<p style="margin: 0px 0px 1.2em ! important;">Thanks for your
reply, Heinz!<br>
I was not aware of the <code style="font-size: 0.85em; font-family: Consolas,Inconsolata,Courier,monospace;margin: 0px 0.15em; padding: 0px 0.3em; white-space: pre-wrap; border: 1px solid rgb(234, 234, 234); background-color: rgb(248, 248, 248); border-radius: 3px; display: inline;">-current</code>
work regarding OpenCL…<br>
By looking at those package and upon reading your response, I
guess this could be the right way to go about it:</p>
<ul style="margin: 1.2em 0px;padding-left: 2em;">
<li style="margin: 0.5em 0px;">publish an ocl-icd package first,
as it is relatively a no-brainer one</li>
<li style="margin: 0.5em 0px;">refactor the current beignet
SlackBuild to not include OpenCL headers by default, leaving
their inclusion as an optional feature</li>
<li style="margin: 0.5em 0px;">publish the resulting beignet
SlackBuild, leaving a suggestion to also install ocl-icd if no
other loader is already installed on the system</li>
</ul>
<p style="margin: 0px 0px 1.2em ! important;">When the next
release of Slackware will be ready, we won’t need to suggest the
ocl-icd package on SBo anymore.<br>
What do you think?</p>
<div
title="MDH:PHA+VGhhbmtzIGZvciB5b3VyIHJlcGx5LCBIZWlueiE8L3A+PHA+SSB3YXMgbm90IGF3YXJlIG9mIHRoZSBgLWN1cnJlbnRgIHdvcmsgcmVnYXJkaW5nIE9wZW5DTC4uLjwvcD48cD5CeSBsb29raW5n
IGF0IHRob3NlIHBhY2thZ2UgYW5kIHVwb24gcmVhZGluZyB5b3VyIHJlc3BvbnNlLCBJIGd1ZXNz
IHRoaXMgY291bGQgYmUgdGhlIHJpZ2h0IHdheSB0byBnbyBhYm91dCBpdDo8L3A+PHA+PGJyPjwv
cD48cD4mbmJzcDstIHB1Ymxpc2ggYW4gb2NsLWljZCBwYWNrYWdlIGZpcnN0LCBhcyBpdCBpcyBy
ZWxhdGl2ZWx5IGEgbm8tYnJhaW5lciBvbmU8L3A+PHA+Jm5ic3A7LSByZWZhY3RvciB0aGUgY3Vy
cmVudCBiZWlnbmV0IFNsYWNrQnVpbGQgdG8gbm90IGluY2x1ZGUgT3BlbkNMIGhlYWRlcnMgYnkg
ZGVmYXVsdCwgbGVhdmluZyB0aGVpciBpbmNsdXNpb24gYXMgYW4gb3B0aW9uYWwgZmVhdHVyZTwv
cD48cD4mbmJzcDstIHB1Ymxpc2ggdGhlIHJlc3VsdGluZyBiZWlnbmV0IFNsYWNrQnVpbGQsIGxl
YXZpbmcgYSBzdWdnZXN0aW9uIHRvIGFsc28gaW5zdGFsbCBvY2wtaWNkIGlmIG5vIG90aGVyIGxv
YWRlciBpcyBhbHJlYWR5IGluc3RhbGxlZCBvbiB0aGUgc3lzdGVtPGJyPjwvcD48cD48YnI+PC9w
PjxwPldoZW4gdGhlIG5leHQgcmVsZWFzZSBvZiBTbGFja3dhcmUgd2lsbCBiZSByZWFkeSwgd2Ug
d29uJ3QgbmVlZCB0byBzdWdnZXN0IHRoZSBvY2wtaWNkIHBhY2thZ2Ugb24gU0JvIGFueW1vcmUu
PC9wPjxwPldoYXQgZG8geW91IHRoaW5rPzwvcD4="
style="height:0;width:0;max-height:0;max-width:0;overflow:hidden;font-size:0em;padding:0;margin:0;"></div>
</div>
<div class="moz-signature">
<pre>Alan Alberghini
SBo clone: <a href="https://github.com/414n/slackbuilds.org">GitHub</a>
</pre>
</div>
<div class="moz-cite-prefix">On 17/04/2017 18:54, Heinz Wiesinger
wrote:<br>
</div>
<blockquote type="cite" cite="mid:3658817.90u8EZmmPO@titania">
<pre wrap="">On Monday, 17 April 2017 18:29:32 CEST 414N wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Greetings,
I’m currently working on a beignet SlackBuild for SBo and I have some
trouble in sorting out how to best manage the package installation.
For the ones who don’t know, beignet <a class="moz-txt-link-rfc2396E" href="https://01.org/beignet"><https://01.org/beignet></a> is Intel’s
own OpenCL implementation for its graphics and CPU hardware. To properly
make use of any OpenCL implementation, one needs:
* an OpenCL ICD loader (|libOpenCL.so|), the entry library that other
software links-to or dynamically loads at runtime
* at least one ICD vendor file(s), to make the relevant OpenCL
implementation installed available to other software through the loader
For systems running solely on Intel CPU/GPU hardware with no other
discrete GPU components (namely, Nvidia/AMD), the installation of the
beignet package would bring:
* the Intel OpenCL implementation + ICD vendor files
* OpenCL headers
The system would still lack the entry point library / ICD loader, but
this could be managed by means of the ocl-icd
<a class="moz-txt-link-rfc2396E" href="https://forge.imag.fr/projects/ocl-icd/"><https://forge.imag.fr/projects/ocl-icd/></a> package (in the making
alongside beignet).
If one has at least another discrete OpenCL-enabled GPU installed on his
system (read, an Nvidia and/or an AMD card), then the scenario becomes a
little more complicated:
* the OpenCL loader is probably provided by the Nvidia/AMD driver
* the OpenCL headers, if any, could be already installed by the
Nvidia/AMD driver package or, hypothetically, provided by a vendor
agnostic package (like the opencl-headers package already on SBo
<a class="moz-txt-link-rfc2396E" href="https://slackbuilds.org/repository/14.2/development/opencl-headers/"><https://slackbuilds.org/repository/14.2/development/opencl-headers/></a>)
All these different requirements/scenario would mean, to me, that the
beignet package should:
* build with/without OpenCL headers
* only suggest the use of the ocl-icd package, as the ICD loader could
already be available on the system
I would really appreciate if anyone could give me insights or thoughts
about this case, especially if I missed something.
Thanks
</pre>
</blockquote>
<pre wrap="">This shows what a mess OpenCL can be. I'm really glad we managed to make this
at least easier for people using -current :)
As a general hint, that's probably also a good place for you to check ;)
Where the headers come from shouldn't matter. They are vendor independent, so
might as well come from a central, generic package. Although the one we have
looks a bit dated.
The ICD loader in -current is ocl-icd. Most OpenCL drivers out there should
work fine with it. Using it as the default ICD loader for scripts on SBo seems
sound for those very reasons.
Grs,
Heinz
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a>
</pre>
</blockquote>
<br>
</body>
</html>