Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <aduskett@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>,
	Samuel Martin <s.martin49@gmail.com>,
	Julien Corjon <corjon.j@ecagroup.com>,
	buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Jesse Van Gavere <jesseevg@gmail.com>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH/next 3/7] package/vulkan-tools: new package
Date: Sat, 2 Sep 2023 12:02:02 +0200	[thread overview]
Message-ID: <20230902120202.53573737@windsurf> (raw)
In-Reply-To: <20230830195446.3958486-3-aduskett@gmail.com>

On Wed, 30 Aug 2023 13:54:42 -0600
Adam Duskett <aduskett@gmail.com> wrote:

> Use $(VULKAN_HEADERS_VERSION) for VULKAN_TOOLS_VERSION as the vulkan packages
> need to all be the same version.
> 
> Signed-off-by: Adam Duskett <aduskett@gmail.com>
> ---
>  DEVELOPERS                             |  1 +
>  package/Config.in                      |  1 +
>  package/vulkan-tools/Config.in         | 17 ++++++++++
>  package/vulkan-tools/vulkan-tools.hash |  3 ++
>  package/vulkan-tools/vulkan-tools.mk   | 47 ++++++++++++++++++++++++++
>  5 files changed, 69 insertions(+)
>  create mode 100644 package/vulkan-tools/Config.in
>  create mode 100644 package/vulkan-tools/vulkan-tools.hash
>  create mode 100644 package/vulkan-tools/vulkan-tools.mk

Applied to next, thanks. I was initially surprised that only vulkaninfo
gets installed but indeed you disable everything else (cube, icd, etc.).

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-09-02 10:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 19:54 [Buildroot] [PATCH/next 1/7] package/vulkan-headers: bump version to 1.3.262 Adam Duskett
2023-08-30 19:54 ` [Buildroot] [PATCH/next 2/7] package/vulkan-loader: new package Adam Duskett
2023-09-02 10:01   ` Thomas Petazzoni via buildroot
2023-08-30 19:54 ` [Buildroot] [PATCH/next 3/7] package/vulkan-tools: " Adam Duskett
2023-09-02 10:02   ` Thomas Petazzoni via buildroot [this message]
2023-08-30 19:54 ` [Buildroot] [PATCH/next 4/7] package/mesa3d: add vulkan broadcom driver support Adam Duskett
2023-09-02 10:02   ` Thomas Petazzoni via buildroot
2023-08-30 19:54 ` [Buildroot] [PATCH/next 5/7] package/mesa3d: add vulkan swrast " Adam Duskett
2023-09-02 10:03   ` Thomas Petazzoni via buildroot
2023-08-30 19:54 ` [Buildroot] [PATCH/next 6/7] package/qt5base: add vulkan option Adam Duskett
2023-09-02 10:03   ` Thomas Petazzoni via buildroot
2023-08-30 19:54 ` [Buildroot] [PATCH vnext 7/7] package/qt6base: " Adam Duskett
2023-09-02 10:03   ` Thomas Petazzoni via buildroot
2023-09-02  9:59 ` [Buildroot] [PATCH/next 1/7] package/vulkan-headers: bump version to 1.3.262 Thomas Petazzoni via buildroot

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=20230902120202.53573737@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aduskett@gmail.com \
    --cc=bernd@kuhls.net \
    --cc=corjon.j@ecagroup.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=jesseevg@gmail.com \
    --cc=romain.naour@gmail.com \
    --cc=s.martin49@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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