All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vincent Davis Jr" <vince@underview.tech>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 2/2] vulkan-validation-layers: add new recipe v1.3.243.0
Date: Sun, 11 Jun 2023 10:53:05 -0700	[thread overview]
Message-ID: <2689.1686505985369486141@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1spFJsRHEWp8PxANdNveD9eu=-4xRFJVhmxjajEPt2_bKA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 507 bytes --]

Yeah, it's related to this issue here

https://lists.openembedded.org/g/openembedded-core/message/173249

And yeah vulkan-validation-layers cmake pulls in the properties set in
SPIRV-ToolsTarget.cmake during the configure stage. The key cmake
property being INTERFACE_LINK_LIBRARIES.

Commit message here should explain more
https://lists.openembedded.org/g/openembedded-core/message/182445

What's BASE_LIB set to on qemu machines? Thought process is that it's
set to "usr/lib" and not "lib".

[-- Attachment #2: Type: text/html, Size: 777 bytes --]

  reply	other threads:[~2023-06-11 17:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 15:13 [PATCH v3 1/2] spirv-tools: fix INTERFACE_LINK_LIBRARIES cmake prop Vincent Davis Jr
2023-06-06 15:13 ` [PATCH v3 2/2] vulkan-validation-layers: add new recipe v1.3.243.0 Vincent Davis Jr
2023-06-09  2:11   ` [OE-core] " Khem Raj
2023-06-09  5:20     ` Vincent Davis Jr
2023-06-09  5:58       ` [OE-core] " Khem Raj
2023-06-09 18:41         ` Vincent Davis Jr
2023-06-09 20:57           ` Vincent Davis Jr
2023-06-11  6:55             ` [OE-core] " Khem Raj
2023-06-11 16:39               ` Khem Raj
2023-06-11 17:53                 ` Vincent Davis Jr [this message]
2023-06-11 17:56                 ` Vincent Davis Jr
2023-06-11 20:30                 ` Vincent Davis Jr

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=2689.1686505985369486141@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 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.