From: "Vincent Davis Jr" <vince@underview.tech>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] vulkan-validation: Add the official Vulkan validation layers
Date: Tue, 27 Jun 2023 12:26:55 -0700 [thread overview]
Message-ID: <28192.1687894015480721156@lists.openembedded.org> (raw)
In-Reply-To: <20230627171028.j6yianz4ppa4skff@amazon.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hey Jordan,
Yeah, the issue turned out to be a property set in SPIRV-ToolsTarget.cmake. Commit bellow should explain
Although ${base_libdir} should of been ${baselib}.
https://lists.openembedded.org/g/openembedded-core/message/182445
Also, renamed recipe to vulkan-validation-layers. Let me know if you have issues everything
looks good in my setup.
https://lists.openembedded.org/g/openembedded-core/message/182446
[-- Attachment #2: Type: text/html, Size: 693 bytes --]
prev parent reply other threads:[~2023-06-27 19:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 20:42 [PATCH 0/3] Add vulkan validation and improvements for headless devices Jordan Crouse
2022-11-10 20:42 ` [PATCH 1/3] spirv-tools: Correctly set the prefix in exported cmake packages Jordan Crouse
2022-11-10 20:43 ` [OE-core] " Khem Raj
2022-11-11 10:44 ` Jose Quaresma
2022-11-10 20:42 ` [PATCH 2/3] vulkan-loader: Allow headless targets to build the loader Jordan Crouse
2022-11-10 20:42 ` [PATCH 3/3] vulkan-validation: Add the official Vulkan validation layers Jordan Crouse
2022-11-10 20:57 ` [OE-core] " Alexander Kanavin
2022-11-10 21:30 ` Jordan Crouse
2022-11-11 8:03 ` Alexander Kanavin
2022-11-11 15:27 ` Jordan Crouse
2022-11-11 17:31 ` Alexander Kanavin
2022-11-13 22:11 ` Alexandre Belloni
2022-11-14 15:23 ` Jordan Crouse
2023-06-01 21:55 ` Vincent Davis Jr
2023-06-02 5:21 ` [OE-core] " Alexander Kanavin
2023-06-27 17:10 ` Jordan Crouse
2023-06-27 19:13 ` Alexander Kanavin
2023-06-27 19:26 ` Vincent Davis Jr [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=28192.1687894015480721156@lists.openembedded.org \
--to=vince@underview.tech \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox