On 12/11/2014 09:20 AM, Jose Fonseca wrote:
On 11/12/14 08:40, Emil Velikov wrote:
Hi Jose,
On 10/12/14 14:18, Jose Fonseca wrote:
I never tried, but it doesn't surprise that ?USE_MGL_NAMESPACE
doesn't work properly on Windows.
At very least the src/mesa/drivers/windows/gdi and
src/gallium/ta
On 11/12/14 08:40, Emil Velikov wrote:
Hi Jose,
On 10/12/14 14:18, Jose Fonseca wrote:
I never tried, but it doesn't surprise that ?USE_MGL_NAMESPACE doesn't work
properly on Windows.
At very least the src/mesa/drivers/windows/gdi and
src/gallium/targets/libgl-gdi targets will fail because t
Hi Jose,
On 10/12/14 14:18, Jose Fonseca wrote:
> I never tried, but it doesn't surprise that ?USE_MGL_NAMESPACE doesn't work
> properly on Windows.
>
>
> At very least the src/mesa/drivers/windows/gdi and
> src/gallium/targets/libgl-gdi targets will fail because the .DEF files there
> explici
Thank you,
I will investigate if I can get a windows build to work, and see how difficult
it is, as we kind of want to have a single process in windows to load both
OpenGL, and Mesa3D at the sometime, and the ability to use either
simultaneously.
Cheers
Jason
From: Jose Fonseca mailto:jfons..
I never tried, but it doesn't surprise that ?USE_MGL_NAMESPACE doesn't work
properly on Windows.
At very least the src/mesa/drivers/windows/gdi and
src/gallium/targets/libgl-gdi targets will fail because the .DEF files there
explicitly request the non-mangled symbols.
Not sure if src/mesa/dr
