rpms / mesa

Clone
Source Code
GIT

#16 D3D12 Gallium Driver support
Opened 2 years ago by nicknas. Modified 2 months ago
rpms/ nicknas/mesa rawhide  into  rawhide

Merge
file modified
+2 -1 
@@ -56,7 +56,7 @@ 
 

  

  Name:           mesa
 

  Summary:        Mesa graphics libraries
 

- %global ver 22.0.1
 

+ %global ver 22.0.2
 

  Version:        %{lua:ver = string.gsub(rpm.expand("%{ver}"), "-", "~"); print(ver)}
 

  Release:        %autorelease
 

  License:        MIT
 
@@ -610,6 +610,7 @@ 
 

  %{_datadir}/vulkan/implicit_layer.d/VkLayer_MESA_device_select.json
 

  %if 0%{?with_vulkan_hw}
 

  %{_libdir}/libvulkan_radeon.so
 

+ %{_datadir}/drirc.d/00-radv-defaults.conf
 

  %{_datadir}/vulkan/icd.d/radeon_icd.*.json
 

  %ifarch %{ix86} x86_64
 

  %{_libdir}/libvulkan_intel.so

file modified
+1 -1 
@@ -1,1 +1,1 @@ 
 

- SHA512 (mesa-22.0.1.tar.xz) = cc8012b8f3fcbecfbb153d0e009e6522c3776023501da8499c06f1eaa9ab0a555ca597e16e4d7a2b954b05c8c0737ae6567e0d8549fb63aa86ae587eb31cd01e
 

+ SHA512 (mesa-22.0.2.tar.xz) = 939ddf9acd280e1b20b3540349b3ad07bbeee5d821198f1d667e86634449bf5d0a0df5832753b8b3f8816709c2f02959cce25f3d26a33cc758dd8e25d158ddb8

As beginning of mesa 21.0 version, mesa started to bring support for d3d12 API calls. So this is a PR to start building this support in the fedora repo, which does not affect to other gallium drivers. Tested over Fedora 34 and 35, with or without d3d12 graphic drivers. Also, I don't know why my PR is no longer considering the d3d12 changes

Hi,

I just looked at the previous PR you had and I think it would all be much cleaner if we had directx-headers packaged separately. This is how Debian and Arch are doing it. See e.g. https://packages.debian.org/source/sid/directx-headers

Any chance you could package it up separately? I can review the new package if needed.

Thanks!

With d3d headers you mean the d3d12-devel package? Maybe it could have another name

Or maybe you mean about to separate those headers from the d3d12-devel package? @pwalter
Edited 2 years ago by nicknas

No I mean to package https://github.com/microsoft/DirectX-Headers project separately as a completely separate source package (not as part of mesa source package) and then our mesa build can use the separately packaged directx-headers-devel as a buildrequires and doesn't need to build the bundled directx stuff as part of the mesa build. It usually tends to work out better in long run if separate upstream projects are packaged separately.

And with completely separate source package I mean to go through https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_Existing_Contributors/ process for the new directx-headers package.

Ok, I will learn more about how to create this new package and upload it. But maybe I don't have permissions to create a whole new repo in rpms

Great! If you are not a packager yet then this is also the process to follow to get packager rights too :)

There's a slightly more involved description of the process for new packagers at https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/

Yeah! I'm new with this hahaha sorry if I'm delaying with this process, but I'm a bit busy these days

No worries at all! Thanks for helping with this.

rebased onto 570fee6
2 years ago

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

I'm not sure to see how this change fit into the current spec file a the post merge probably do not display the merge request as it should (it should have been probably rebased manually instead).

I've provided an alternate implementation at https://src.fedoraproject.org/rpms/mesa/pull-request/41
Metadata
None
No Tags
Changes Summary 2
+2 -1
file changed
mesa.spec
+1 -1
file changed
sources
Powered by Pagure 5.13.3
Documentation • File an Issue • About this Instance • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.