Re: mxe-octave status

[Philip Nienhuis]

Philip Nienhuis wrote:
> John W. Eaton wrote:
> > On 10/20/2017 06:00 PM, John W. Eaton wrote:
> > > On 10/20/2017 04:28 PM, Philip Nienhuis wrote:
> > >
> > > > Ah, I see I misunderstood; you mean that mesa version provokes a
> > > > segfault.
> > > > (Sorry for not following the whole issue in detail - which relates to
> > > > not having hit the issue with older system opengl32.dll libs yet.)
> > >
> > > No, the mesa version works fine for me.  It's when I've built the qt5
> > > version with mesa and then I attempt to use the system opengl32.dll
> > > instead.  As far as I know, this should work since the API should be
> > > the same.  It's supposed to be a "drop-in replacement"

Results with a --disable-system-opengl32 mxe-octave build:

I can confirm the crash on a PC with older Intel card (with the default 
Windows opengl32.dll) when removing / renaming the Octave-supplied 
(mesa-)opengl32.dll. Octave works fine there with the mesa-openg32.dll

On any system, __opengl_info__ doesn't work the first time. But the 
second time, or after having made a simple "plot (1:10)", 
__opengl_info__ does work.
So apparently there's some initialization issue. It doesn't matter which 
opengl32.dll (Octave, system) is in use.

Earlier builds (octave & mxe-octave hg-id's) had the same issue; when 
running __run_test_suite__ I usually got a FAIL for __opengl_info__ but 
afterwards, "test __opengl_info__" worked.

Philip