Package Details: spirv-tools-git 2023.1+8.gcdc4e528f3-1

Git Clone URL: (read-only, click to copy)
Package Base: spirv-tools-git
Description: API and commands for processing SPIR-V modules
Upstream URL:
Licenses: custom
Conflicts: spirv-tools
Provides: spirv-tools
Submitter: 1ace
Maintainer: 1ace (Lone_Wolf)
Last Packager: Lone_Wolf
Votes: 7
Popularity: 0.000000
First Submitted: 2016-02-16 22:53 (UTC)
Last Updated: 2023-01-21 16:00 (UTC)

Required by (30)

Sources (1)

Latest Comments

1 2 Next › Last »

Lone_Wolf commented on 2023-01-21 16:04 (UTC)

Done, the change was very similar to that.

/usr/bin/ uses a sh-shebang, so I added sh as dependency for completeness.

1ace commented on 2023-01-19 19:48 (UTC)

Lone_Wolf: made you a co-maintainer; feel free to try to make it use spirv-headers-git (probably just changing $srcdir to /usr/include on line 31) :)

Lone_Wolf commented on 2023-01-13 11:31 (UTC) (edited on 2023-01-13 11:36 (UTC) by Lone_Wolf)

confirmed also happens with spirv-headers-git .

Looks like Khronos or github made changes in the setup.

Remove the local copy of the git repo and start with a fresh one.

(If you depend on spirv-headers-git like me, fix that first then spirv-tools-git .)

Aryma commented on 2023-01-12 20:10 (UTC) (edited on 2023-01-12 20:11 (UTC) by Aryma)

warning: remote HEAD refers to nonexistent ref, unable to checkout

==> Starting pkgver()...

fatal: Not a valid object name HEAD

==> ERROR: pkgver is not allowed to be empty.

==> ERROR: pkgver() generated an invalid version:

I get this error

Lone_Wolf commented on 2022-12-09 22:47 (UTC)

In the PKGBUILD you download spirv-headers trunk and build against it.

However in depends you list spirv-headers which is a different version .

Maybe you could depend on aur spirv-headers-git instead and skip downloading spirv-headers completely ?

1ace commented on 2022-06-22 08:57 (UTC)

@Aryma: ah sorry, when I was on my phone I missed it, but now that I'm back on my laptop I can see that there are actually some unannotated tags such as the sdk-* one that upstream added a few days ago.

I have now removed --tags to ignore unannotated tags (it hasn't been needed in 2 years, last time upstream did that was in February 2019), and added --match 'v*.*' to only consider these tags and not anything else upstream might throw at us again.

Thanks for reporting the issue! 🙏

1ace commented on 2022-06-20 14:41 (UTC)

@Aryma: that tag is in the SPIRV-Headers repo, but pkgver() is explicitly looking at SPIRV-Tools; I don't understand how you could have gotten there?

Aryma commented on 2022-06-16 22:32 (UTC) (edited on 2022-06-16 22:33 (UTC) by Aryma)

i get this error :

Cloning spirv-tools-git build files...
Generating spirv-tools-git information...
Checking spirv-tools-git dependencies...
Warning: downgrading package spirv-tools-git (2022.2+31.g8f7f5024f8-1 => 2022.2-1)
Resolving dependencies...
Checking inter-conflicts...

Building spirv-tools-git...
==> Making package: spirv-tools-git 2022.2-1 (Thu Jun 16 23:30:15 2022)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating SPIRV-Tools git repo...
Fetching origin
  -> Updating SPIRV-Headers git repo...
Fetching origin
==> Validating source files with sha1sums...
    SPIRV-Tools ... Skipped
    SPIRV-Headers ... Skipped
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of SPIRV-Tools git repo...
Cloning into 'SPIRV-Tools'...
  -> Creating working copy of SPIRV-Headers git repo...
Cloning into 'SPIRV-Headers'...
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: sdk+ 

1ace commented on 2021-01-02 14:20 (UTC)

Hey @shoober420!
You're right, and there's also a number of other issues with this package, sorry, I kinda forgot about it and left it to rot :/

This package has now been updated with your suggestion as well as a number of other things, which means it is now completely interchangeable with its "release package" counterpart in [extra] :)

shoober420 commented on 2020-12-27 17:06 (UTC)

Thank you for this package.

Could you please add the “ -DBUILD_SHARED_LIBS=ON” fag to the build section?