PDA

View Full Version : Mesa3d installing for Windows 10



Lam777
12-18-2016, 04:10 AM
Hello,

I don't understand the installing guide from Mesa 3d (Homepage from Mesa 3d)
I have already downloaded Mesa 13.02, Python 2.7.12 and SCons 2.5.1.

Thanks for request !

Lam

Dark Photon
12-18-2016, 07:37 PM
Your best bet for help building/installing on Windows is probably the Mesa3D mesa-users mailing list:

* http://www.mesa3d.org/lists.html

You might even find someone that will share some precompiled binaries so you can just skip building and go straight to using Mesa3D. However, I see that they're recommending you try here first :-)

Which part are you having trouble with?:

* http://www.mesa3d.org/install.html

Cola77
01-12-2017, 12:52 PM
I have also this problem.

I think he don't understand like me what they me with that installing guide:



To build Mesa with SCons on Linux or Windows do

scons
The build output will be placed in build/platform-machine-debug/..., where platform is for example linux or windows, machine is x86 or x86_64, optionally followed by -debug for debug builds.

To build Mesa with SCons for Windows on Linux using the MinGW crosscompiler toolchain do

scons platform=windows toolchain=crossmingw machine=x86 libgl-gdi
This will create:

build/windows-x86-debug/gallium/targets/libgl-gdi/opengl32.dll Mesa + Gallium + softpipe (or llvmpipe), binary compatible with Windows's opengl32.dll
Put them all in the same directory to test them.

Lam777
01-14-2017, 01:14 PM
Yes, Cola77 ist right.
I don't understand, what they mean about that.

Lam777
01-14-2017, 01:18 PM
The best would be, if you let me download a opengl32.dll file with full OpenGl 3.3 support.
That is the thing I need for my Windows 10 PC.
--> I don't want to buy a new graphic card.


Thanks !

mhagain
01-15-2017, 11:59 AM
The best would be, if you let me download a opengl32.dll file with full OpenGl 3.3 support.
That is the thing I need for my Windows 10 PC.
--> I don't want to buy a new graphic card.


Thanks !

OpenGL doesn't work that way. OpenGL is not software.

If you want hardware accelerated graphics then you must use the driver for your graphics card. If the driver for your graphics card does not support a particular GL version then you cannot have it hardware accelerated. This isn't about letting you do it or preventing you from doing it. It just does not work that way.

Mesa is a software implementation. It is not a good alternative if you want performance. You will be disappointed.

Lam777
01-17-2017, 12:18 PM
I need Mesa for a programm which need OpenGl 3.3.
So I will be happy with Mesa although it's not the best support.


Thanks for request !

Dark Photon
01-17-2017, 05:14 PM
I need Mesa for a programm which need OpenGl 3.3.
So I will be happy with Mesa although it's not the best support.

Your best bet for that is probably the Mesa3D (http://www.mesa3d.org/[/url) mesa-users (http://www.mesa3d.org/lists.html) mailing list.

Lam777
01-18-2017, 07:10 AM
Thanks, I have already do it now.

But it would the best way for me anyway, if somebody had a guide for me.

pal1000
02-26-2017, 09:11 AM
A better guide to build mesa was written by some folks at QT (https://wiki.qt.io/MesaLlvmpipe). They posted it on their Wiki.
I took that guide and automated the process. I went so far that I created a complete installer (https://github.com/pal1000/mesa-dist-win/releases).
It installs mesa3d system-wide and also an utility for local deployments as certain applications may be confused.

Lam777
04-10-2017, 01:21 AM
Thank you very much !

But I have a question:

Do you have a way that your build can support OpenGL 3.3 fully (shading language 3.3) ?

That would be very nice :)

Dark Photon
04-10-2017, 06:56 AM
If you want Mesa3D source or binaries, you need to get that from the Mesa3D web site (https://www.mesa3d.org/download.html) or request it on the Mesa3D mailing list.

For information on installing OpenGL for various GPU vendors, see: Getting Started (https://www.khronos.org/opengl/wiki/Getting_Started) in the OpenGL wiki.

Lam777
04-18-2017, 01:37 PM
I don't understand what they are meaning here (for OpenGl 4.5.).

OpenGL 4.5 is only available if requested at context creation because compatibility contexts are not supported.

https://www.mesa3d.org/relnotes/17.0.2.html

Dark Photon
04-18-2017, 03:49 PM
It sounds like only an OpenGL 4.5 Core Profile context is supported, not an OpenGL 4.5 Compatibility Context.

You can only get a core context by requesting one when you create the context. For details, see:

* Creating an OpenGL Context (WGL) (https://www.khronos.org/opengl/wiki/Creating_an_OpenGL_Context_(WGL))
* Tutorial: OpenGL 3.0 Context Creation (GLX) (https://www.khronos.org/opengl/wiki/Tutorial:_OpenGL_3.0_Context_Creation_(GLX))

Lam777
04-19-2017, 11:45 AM
What programm should I use ?

pal1000
04-28-2017, 11:02 AM
Thank you very much !

But I have a question:

Do you have a way that your build can support OpenGL 3.3 fully (shading language 3.3) ?

That would be very nice :

What programm should I use ?

No program. You have to use an environment variable. See documentation (https://www.mesa3d.org/envvars.html).
The one of interest is MESA_GL_VERSION_OVERRIDE. The documentation is unfortunately incomplete as it doesn't state you can request a compatibility context with CONTEXTCOMPAT. Ex. 3.3COMPAT for OpenGL 3.3. Putting something like this in a batch file that also launches your game/program you want to use Mesa with should do the trick:

set MESA_GL_VERSION_OVERRIDE=3.3COMPAT
filename.exe

The documentation only mentions core and core+forward compatible contexts. These are unlikely to be used by Windows applications because all Windows graphics drivers that support OpenGL 3.1 and up implement GL_ARB_compatibility leading to default on compatibility contexts. Most exceptions are cross-platform applications that support at least Windows and a form of Unix (Linux, Mac, etc). These have to request core contexts for cross-platform compatibility to work, because on Unix things are completely different. Contexts have to be requested explicitly by programs and Mesa demands the same thing and as explained above is not something to see often on Windows. That's why we need that variable set to override Mesa default behavior with what's the default on Windows.

Lam777
05-08-2017, 11:30 PM
And what should I set ? I have used your build.

Thanks !


(Sorry, I don't know much.)

pal1000
05-10-2017, 10:13 AM
Wrote a few examples. I'll come with a complete guide soon.
Look here: https://github.com/pal1000/mesa-dist-win/tree/master/glcontextsamples

JamilaKropp
06-02-2017, 09:30 AM
Wrote a few examples. I'll come with a complete guide soon.
Look here (http://mega-joker-slot.com): https://github.com/pal1000/mesa-dist-win/tree/master/glcontextsamples

Wow, that really helped.
Is the complete guide still coming?

pal1000
06-03-2017, 02:31 PM
It is already posted here since May 26, last updated May 29:
https://github.com/pal1000/mesa-dist-win/blob/master/readme.md#manual-opengl-context-configuration

Lam777
07-26-2017, 03:38 AM
So now I just have to done this (from the beginning) :

1. I use your complete installer.
2. I use your desmume.cmd file.
3. I use your desmume2.cmd file.

Is that right ?

(I have Opengl 3.1)

pal1000
07-29-2017, 04:11 AM
If Desmume is what you want to run you should know that built-in software rasterizer is a bit faster than OpenGL 3.2 renderer + llvmpipe. OpenGL Old + llvmpipe exhibits graphics corruptions.
At least this is how it behaves on my system. As for desmume.cmd and desmume2.cmd you should pick just one of them.
As I said in the manual context configuration guide examples section (https://github.com/pal1000/mesa-dist-win/blob/master/glcontextsamples/readme.txt), there are 2 ways to get OpenGL 3.2 working and you need to pick only one of them.