Error loading zink DLLs #205
Replies: 9 comments 12 replies
-
Beta Was this translation helpful? Give feedback.
-
Is there an option to build ARM64 version of mesa ? |
Beta Was this translation helpful? Give feedback.
-
I am able to build the mesa project using build.cmd. After the build, command prompt automatically closes. I am trying to recompile the mesa using ninja but it fails.
How do I rebuild just mesa after making some changes in mesa code ? |
Beta Was this translation helpful? Give feedback.
-
I am trying to rebuild the mesa after making some changes using build.cmd but it exits with error:
Full logs:
|
Beta Was this translation helpful? Give feedback.
-
Can you try without enabling futex. That wasn't tested sufficiently in recent time with futex being disabled per #112 poll results. |
Beta Was this translation helpful? Give feedback.
-
There's another common issue observed with the build. Every time I change mesa build parameters. It gives an error: `
` |
Beta Was this translation helpful? Give feedback.
-
Something is seriously wrong at your end with Python virtual environment creation. Try these first:
More things to try if this doesn't help;
Updating python automatically triggers mesa-dist-win python virtual environment rebuild so you don't need to worry about forgetting to remove |
Beta Was this translation helpful? Give feedback.
-
Can you please let me know what all flags were enabled while building the 24.2.6 release DLLs ? |
Beta Was this translation helpful? Give feedback.
-
How can i build mesa.sln solution file from vs code using Debug configuration ? I wanna generate debug binaries of mesa with pdb's and perform local/remote debugging from VS. |
Beta Was this translation helpful? Give feedback.
-
I am running an app called gfxbench on adreno GPU on windows. Trying to test zink.
When I copy prebuilt gallium DLLs(from pal1000) next to gfxbench, gfxbench list 'OpenGL with zink vulkan'
But when I build gallium DLLs on my device and copy next to gfxbench, it doesn't list 'OpenGL with zink vulkan'
Steps to run:
set GALLIUM_DRIVER=zink
gfxbench.exe
I am using meson build command to build the DLLs :
meson setup builddir/ --backend=vs -Dbuildtype=release -Dgallium-drivers=zink -Dopengl=true -Dshared-glapi=enabled
When I look at the file size of libgallium_wgl.dll, opengl32.dll and libglapi.dll , it differs a lot.
Prebuilt from pal1000
libgallium_wgl.dll : 52MB
opengl32.dll : 134KB
libglapi.dll : 332KB
My build
libgallium_wgl.dll : 49MB
opengl32.dll : 44KB
libglapi.dll : 205KB
Could you please help me out with the build steps that you've followed ?
Beta Was this translation helpful? Give feedback.
All reactions