Mesa is a 3-D graphics library with an API which is very similar to that of OpenGL.*
Mesa is a 3-D graphics library with an API which is very similar to
that of OpenGL.* To the extent that Mesa utilizes the OpenGL command
syntax or state machine, it is being used with authorization from
Silicon Graphics, Inc.(SGI). However, the author does not possess an
OpenGL license from SGI, and makes no claim that Mesa is in any way a
compatible replacement for OpenGL or associated with SGI. Those who
want a licensed implementation of OpenGL should contact a licensed
vendor.
Please do not refer to the library as MesaGL (for legal reasons). It's
just Mesa or The Mesa 3-D graphics library.
* OpenGL is a trademark of Silicon Graphics Incorporated.
- Devel package for openSUSE:Factory
-
140
derived packages
- Links to openSUSE:Factory / Mesa
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout X11:XOrg/Mesa && cd $_ - Create Badge
Refresh
Refresh
Source Files (show merged sources derived from linked package)
| Filename | Size | Changed |
|---|---|---|
| Mesa-rpmlintrc | 0000000523 523 Bytes | |
| Mesa.changes | 0000339936 332 KB | |
| Mesa.keyring | 0000398858 390 KB | |
| Mesa.spec | 0000041122 40.2 KB | |
| README-suse-maintenance.md | 0000000428 428 Bytes | |
| README.updates | 0000000413 413 Bytes | |
| U_fix-mpeg1_2-decode-mesa-20.2.patch | 0000000807 807 Bytes | |
| _constraints | 0000000569 569 Bytes | |
| _link | 0000000139 139 Bytes | |
| _multibuild | 0000000056 56 Bytes | |
| baselibs.conf | 0000004833 4.72 KB | |
| manual-pages.tar.bz2 | 0000137685 134 KB | |
| mesa-24.2.6.tar.xz | 0029568568 28.2 MB | |
| mesa-24.2.6.tar.xz.sig | 0000000310 310 Bytes | |
| n_add-Mesa-headers-again.patch | 0000000615 615 Bytes | |
| n_drirc-disable-rgb10-for-chromium-on-amd.patch | 0000001234 1.21 KB | |
| n_stop-iris-flicker.patch | 0000000970 970 Bytes | |
| paste-1.0.14.tar.gz | 0000018157 17.7 KB | |
| proc-macro2-1.0.86.tar.gz | 0000048958 47.8 KB | |
| python36-buildfix1.patch | 0000002548 2.49 KB | |
| python36-buildfix2.patch | 0000000533 533 Bytes | |
| quote-1.0.33.tar.gz | 0000028090 27.4 KB | |
| syn-2.0.68.tar.gz | 0000265035 259 KB | |
| tlsdesc_test.patch | 0000000811 811 Bytes | |
|
u_0001-intel-genxml-Drop-from-__future__-import-an |
0000001730 1.69 KB | |
|
u_0002-intel-genxml-Add-a-untyped-OrderedDict-fall |
0000003099 3.03 KB | |
| u_dep_xcb.patch | 0000000642 642 Bytes | |
| u_mesa-CVE-2023-45913.patch | 0000000471 471 Bytes | |
| u_mesa-CVE-2023-45919.patch | 0000001199 1.17 KB | |
| u_mesa-CVE-2023-45922.patch | 0000000688 688 Bytes | |
| unicode-ident-1.0.12.tar.gz | 0000042168 41.2 KB |
Comments 66
Is there any chance to get the build for 13.2 fixed in this repository? There seems to be no unresolvable technical show stopper: https://build.opensuse.org/package/show?project=home%3Aaevseev&package=Mesa
Of course this would be possible despite openSUSE 13.2 will be out of support pretty soon. Seems you removed U_cso-don-t-release-sampler-states-that-are-bound.patch. Not sure why? For the additional patch fix-missing-memfd-header.patch, please follow our X11:XOrg patch guidelines. After resolving this you can open a submitrequest against X11:XOrg. Thanks!
I did neither remove anything nor add any patch - you seem to mistake me for the maintainer of the repository I mentioned. My motivation for asking is simply not to let increase the number of repositories I use (currently 49 and counting) any further by adding another "home/" repository for packages at least theoretically already available in a repository in use.
Indeed I assumed this would be your repository.
Thanks for having revivified providing updated packages for 13.2.
will this bump to version 17.1?
17.2.3 release is cut https://github.com/mesa3d/mesa/releases/tag/mesa-17.2.3
Could the build be enabled for openSUSE Leap 42.3 to get a Mesa 18 version for this distribution?
Currently it's not possible, since llvm cannot be built for openSUSE 42.3. :-(
OK. Thank you for your answer.
Do you think it would be possible to build it anytime soon for openSUSE Leap 42.3? Or will it stay at the current offered Mesa version for this distribution?
I can't say. A collegue is/was working on this. But it has no high priority.
probably not, Newer versions of Mesa also need new version of Wayland libs and protocols. + Bonus six months after the release of Leap 15.0, 42.3 Leap will EOL
Ok. Build against Leap 42.3 is enabled in X11:XOrg again. Looks good so far.
This comment has been deleted
On my TODO list ...
This comment has been deleted
Looks like this came in with some autocommit magic crap back from factory. :-(
r773 | buildservice-autocommit | 2018-09-18 09:37:23 | 0273904b5d3bac6a229ef7bd5bf12077 | unknown | rq635013
baserev update by copy to link target
r772 | buildservice-autocommit | 2018-09-11 15:12:48 | 04666deac08cb6669a4cfb681e18d754 | unknown | rq631796
baserev update by copy to link target
Fortunately Tobias Klausmann brought this back, now to 18.2.1 ...
Please add GALLIUM_HUD support for intel drivers
Intel drivers aren't using gallium at the moment. Not sure what you mean here.
Please check/fix %arm and aarch64 before pushing to Factory
This comment has been deleted
@ryanbach Already checked in ... :-)
This comment has been deleted
done. :-)
This comment has been deleted
Thanks. Sounds good! An appropriate submitrequest would be appreciated and accepted. ;-)
Is the current (2020-01-09) state of Mesa in this repo supposed to work? There's a mixture of 19.3.1 (e.g. Mesa) and 19.2.6 (e.g. Mesa-dri) packages online - I had to go back to Leap 15.1's Mesa 18.3.2 to get the GUI up and running …
Thanks. Indeed build of Mesa-driver on Leap 15.1/15.2 fails due to llvm version < 8. I'm trying to build llvm8 for Leap 15.1/15.2. Will take some time though ...
No need to hurry (at least not because of me). Just wanted to know if I broke something on my side or if the repo's the one to blame … ;)
It has been the Mesa update to 19.3.1 .... which now needs llvm 8 ...
@akilgus Meanwhile build against Leap 15.0/15.1 fixed. :-)
Thanks for your work. I'll give the new packages a try within the coming days.
This comment has been deleted
Already on my TODO list. ;-)
Can we enable the MESA_VK_DEVICE_SELECT layer and the Mesa Vulkan Overlay layer for the Tumbleweed package?
Hmm. Could you come up with a concrete proposal for the package, preferrably a submit request? My guess is that I need to add -Dvulkan-device-select-layer=true as option for meson in specfile, but since you're apparently an expert here, it would be good if you could come up with something well tested.
I have branched the package and tried out some changes. They are in my obs repository here: https://build.opensuse.org/package/show/home:zakhrov:Mesa/Mesa It adds 2 packages. Mesa-vulkan-overlay and Mesa-vulkan-device-select which has the libraries and JSON files
I have submitted a request for it
I've tried updating to 21.0.1.
meson.build:21:0: ERROR: Value classic is not boolean (true or false)Valid values for -Dosmesa have changed. And a lot more. Mesa update won't be trivial this time. I tried for about two hours, but gave up then. May take several days to update Mesa this time. :-(
-Dosmesa=classic \is no longer being used. Removed that option and now noticeERROR: Options "swrast" are not in allowed choices: "auto, i915, i965, r100, r200, nouveau"Looks like mesa has removed it https://www.phoronix.com/scan.php?page=news_item&px=Mesa-Kills-SWRAST
n_drirc-disable-rgb10-for-chromium-on-amd.patch is unneeded as it got fixed in gstreamer a few months ago:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/-/merge_requests/410
Thanks. Done. See my latest changelog entry for Mesa sources.
The Crocus driver(Intel 965G(Gen4)-Haswell(Gen7.5 and also Cherryview) Gallium-based driver) has been forgotten in the Spec files.
//-----------------------------------------
%ifarch %{ix86} x86_64
-Ddri-drivers=i915,i965,nouveau,r100,r200 \
-Dgallium-drivers=r300,r600,radeonsi,nouveau,swrast,svga,virgl,iris,crocus \
//------------------------------------------
Currently, the Crocus isn't enabled by default in Mesa 21.2
//------------------------------------------
mesa/meson_options.txt
option( 'prefer-crocus', type : 'boolean', value : false, description : 'Prefer new crocus driver over older i965 driver for gen4-7' )
//---------------------------------------
And users who want to use the Crocus driver should set the 'MESA_LOADER_DRIVER_OVERRIDE=crocus' environment variable, And if there is a problem with video hardware acceleration(vaapi driver), Should set the 'LIBVA_DRIVER_NAME=i965'
Enabled. But currently build on %ix86 fails. This is the bigger issue right now.
Thanks
I'm not a Mesa contributor, But I took a quick look and personally suspected GCC11.x(This is just a guess) because build with GCC7.x is successful(Leap_15.2 Mesa) but fails with GCC11.x, And also I remembered some opened issues on Mesa Gitlab that seems to be related to the GCC11
https://gitlab.freedesktop.org/mesa/mesa/-/issues/5069 https://gitlab.freedesktop.org/mesa/mesa/-/issues/5067 https://gitlab.freedesktop.org/mesa/mesa/-/issues/5068
Thanks. I'm just wondering why Mesa 21.1.6 can still be built on %ix86 with GCC11 in place. So it needs to be related to changes in Mesa 21.2.0.
The issue seems to be solved; Please checks Spec and conf files in my branch. https://build.opensuse.org/package/show/home:BehzadA:branches:X11:XOrg/Mesa Based on https://build.opensuse.org/package/show/home:tobijk:X11:XOrg:Unstable/Mesa Modified by me and need to be reviewed and also "Mesa-dri-kmsro" build is enabled.
Thanks! I've fixed the build against %ix86 now by removing "-flto=auto" from cpp flags.
The i915g driver(Intel Gen3 Gallium-based driver) has been forgotten in the Spec files.
%ifarch %{ix86} x86_64
-Ddri-drivers= \ -Dgallium-drivers=r300,r600,radeonsi,nouveau,swrast,svga,virgl,iris,crocus,i915 \Also to support legacy platforms that only have classic drivers and Swrast driver
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10557 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8069/
I'm not aware of an (open)SUSE platform, which only supported classic drivers and swrast drivers. I don't want to readd no longer upstream supported classic drivers.
I wasn't aware of the i915 Gallium driver for Intel Gen3 GPUs. I'll try to add it.
Can we enable zink driver in this repo?
Just accepted your submit request. :-)
Hello, mesa 23.1 was released 13 days ago https://lists.freedesktop.org/archives/mesa-announce/2023-May/000720.html
I tried updating to it, but build fails. https://build.opensuse.org/project/show/home:sndirsch:branches:X11:XOrg
this->valueis a union. You might want to use&this->value.u64instead. The compiler should understand it then.Thanks @gladiac. Hmm, could you be a bit more code specific?
@sndirsch
I posted a diff from the latest successful build from home:X0F:HSF. https://pastebin.com/AzR8pwja Massive differences between the 2 spec files.
Thanks @kbeast89. Unfortunately these are radical changes I cannot apply. Any chance you limit this to the change, which just fixes the build in X11:XOrg?
You need to build Mesa-drivers with
-Dshader-cache=enabledand Mesa with-Dxlib-lease=enabled, that should allow a successful build. Also recommend-Dallow-kcmp=enabledfor both packages, to avoid some scary messages when comparing fds.Check https://build.opensuse.org/package/show/home:llyyr:branches:home:sndirsch:branches:X11:XOrg/Mesa (currently it's failing because there's no gbm.h to remove after successful build but that should be an easy fix)
w.r.t to the note mentioning NVK in the changelog see these two posts by one of the devs:
https://mastodon.gamedev.place/<at>gfxstrand/111519395059895929 https://mastodon.gamedev.place/<at>gfxstrand/111520029598520783
edit: replaced @ in the link with <at> because the link is mangled otherwise
@sndirsch Hi, are there any plans to enable the Meson build option of "-Dintel-xe-kmd=enabled" for the Xe driver?
I can't find such a meson variable in Mesa 24.1.2. Are you sure it still exists and is still needed to set it? I think I've read about such a meson variable on Phoronix when the driver wasn't considered stable yet.
@sndirsch Looks like it was enabled by default in 24.0.5 - intel: Enable Xe KMD support by default. Apologies for the noise.