On Fri, 24 Feb 2023 at 13:29, Alexandre Belloni via
lists.openembedded.org
<alexandre.belloni=bootlin....@lists.openembedded.org> wrote:
> > -PACKAGECONFIG[opencl] = "-Dgallium-opencl=icd -Dopencl-spirv=true 
> > ${OPENCL_NATIVE},-Dgallium-opencl=disabled -Dopencl-spirv=false,libclc 
> > spirv-tools"
> > +PACKAGECONFIG[clover] = "-Dgallium-opencl=icd -Dopencl-spirv=true 
> > ${OPENCL_NATIVE},-Dgallium-opencl=disabled -Dopencl-spirv=false,libclc 
> > spirv-tools"
>
> Are we allowed to do that? It will break anyone using "opencl" in there
> PACKAGECONFIG

It's a part of the implicit agreement that bumping master revision to
a newer master revision can and does break stuff.

In this case 'opencl' is ambigous about what opencl implementation you
get. Curl's 'ssl' option was recently renamed to 'openssl' for the
same reason, and broke builds similarly.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177685): 
https://lists.openembedded.org/g/openembedded-core/message/177685
Mute This Topic: https://lists.openembedded.org/mt/97202945/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to