Re: mxe-octave status

[John W. Eaton]

On 10/20/2017 05:32 AM, PhilipNienhuis wrote:

> FWIW, in latest Octave 4.3.0+ built with qt5 and up-to-date mxe-octave incl.
> your mesa patches, _opengl_info__ runs fine & relatively fast with NVidia
> graphics hardware en newer Intel hardware (all with OpenGL v. 3.3.0) on my
> Windows boxes at home.

What HG ID for mxe-octave?  How did you configure mxe-octave?  Did you 
use --disable-system-opengl when configuring mxe-octave?  Do you have 
opengl32.dll in the bin directory alongside octave-gui.exe?
Are you using the mesa software renderer provided by the mesa 
opengl32.dll or the accelerated hardware renderer?

> At work, with older Intel HW and with virtualized sessions ("VMWare VGA 3D"
> graphics adapter), that same Octave build only freezes the first time when
> invoking __opengl_info__ or any plot function, after that my Windows
> installations issue messages that they detected problems with Octave and
> have automatically applied "compatibility settings" to it. To no avail as
> the next time graphics functions are invoked Octave just crashes immediately
> - indeed a segfault AFAICS.
> Do I suppose correctly those crashes are due to the mesa patches?

I don't know, because I don't understand exactly what it is you are 
doing.  Are you using the opengl32.dll that is in the bin directory 
along with Octave, or are you using the opegl32.dll provided by the 
operating system or hardware vendor?

> Could Octave be learned the same trick? that is, disabling hardware OpenGL
> if it finds "non-compatible graphics HW" ? Probably be too much trouble if
> that would only be required for Windows.

That's exactly the point of building and providing our own mesa 
opengl32.dll, to avoid the hardware problems by doing software rendering 
instead.  But we are not currently attempting to detect configurations 
that might have problems and automatically choose between the mesa DLL 
and the one provided by the system.

jwe