All of 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 2/7] package/vulkan-loader: new package
Date: Sat, 2 Sep 2023 12:01:33 +0200	[thread overview]
Message-ID: <20230902120133.71a0809c@windsurf> (raw)
In-Reply-To: <20230830195446.3958486-2-aduskett@gmail.com>

Hello Adam,

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

> diff --git a/package/vulkan-loader/vulkan-loader.hash b/package/vulkan-loader/vulkan-loader.hash
> new file mode 100644
> index 0000000000..e09ecda8a9
> --- /dev/null
> +++ b/package/vulkan-loader/vulkan-loader.hash
> @@ -0,0 +1,3 @@
> +# Locally calculated
> +sha256  3bbaa5ee64058a89949eb777de66ce94bfe3141892514172cfc9451c756802d5  vulkan-loader-1.3.262.tar.gz
> +sha256  43c0a37e6a0fa7ff3c843b3ec5a4fac84b712558ddac103fbd4c1649662a9ece  LICENSE.txt
> diff --git a/package/vulkan-loader/vulkan-loader.mk b/package/vulkan-loader/vulkan-loader.mk
> new file mode 100644
> index 0000000000..d87e57ebd4
> --- /dev/null
> +++ b/package/vulkan-loader/vulkan-loader.mk
> @@ -0,0 +1,45 @@
> +################################################################################
> +#
> +# vulkan-loader
> +#
> +################################################################################
> +
> +VULKAN_LOADER_VERSION = $(VULKAN_HEADERS_VERSION)
> +VULKAN_LOADER_SITE = $(call github,KhronosGroup,Vulkan-Loader,v$(VULKAN_LOADER_VERSION))
> +VULKAN_LOADER_LICENSE = Apache-2.0
> +VULKAN_LOADER_LICENSE_FILES = LICENSE.txt
> ++VULKAN_LOADER_INSTALL_STAGING = YES

  ^^^ typo here, there was a "+" at the beginning of the line. Funnily,
  make did not complain about this, and just ignored this line, so
  vulkan-loader was not installed into staging.

I fixed that and applied to next. However, could you have a look at
whether we need to keep /usr/share/vulkan/registry/? It contains
JSON/Python stuff, I don't think it's useful at runtime?

Also, what is /usr/share/vulkan/icd.d/ ? I see there's an ICD tool in
vulkan-tools. Is that related? Needed on the target?

Thanks!

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

  reply	other threads:[~2023-09-02 10:01 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 [this message]
2023-08-30 19:54 ` [Buildroot] [PATCH/next 3/7] package/vulkan-tools: " Adam Duskett
2023-09-02 10:02   ` Thomas Petazzoni via buildroot
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=20230902120133.71a0809c@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 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.