From: "Michael Lynch" <mlynch@hi-techniques.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: Dependencies ?
Date: Fri, 24 May 2024 08:33:38 -0700 [thread overview]
Message-ID: <18579.1716564818242640497@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_XF0cXbK-nVeK=xpd8_XC07j-FC8rovvips085M1OMHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
For informational purposes the two recipes in question here are intel-compute-runtime and intel-graphics-compiler. Both are items needed to use OpenCL with INTEL GPUs.
Alex, it sounds like the "wrong" thing to do is to "rollback" the meta-clang layer back to the "mickledore" branch as was suggested? Here's the weird thing, the layer compatibility for meta-clang in the "mickledore" branch actually lists "scarthgap" in addition to "mickeldore" and one other. Where as layer compatibility of meta-clang in the "scarthgap" branch is set to "scarthgap" only. Did someone maybe do the wrong thing with layer compatibility in meta-clang on the mickledore branch? Just curious because it seemed that mixing layer branches to make things build seemed a bit off of the whole philosophy of how yocto/bitbake was intended to work but I thought maybe that was just me not understanding everything completely.
-- Mike
[-- Attachment #2: Type: text/html, Size: 979 bytes --]
next prev parent reply other threads:[~2024-05-24 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 13:57 Dependencies ? Michael Lynch
2024-05-24 14:14 ` [bitbake-devel] " Quentin Schulz
2024-05-24 14:59 ` Alexander Kanavin
2024-05-24 15:33 ` Michael Lynch [this message]
2024-05-24 17:06 ` Alexander Kanavin
2024-05-27 3:50 ` Mittal, Anuj
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=18579.1716564818242640497@lists.openembedded.org \
--to=mlynch@hi-techniques.com \
--cc=bitbake-devel@lists.openembedded.org \
/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.