While, in spite of the recent improvements by jwe, the interpreter doesn't have a reasonable speed there is a tendency towards upgrading to the latest llvm version. I believe that here the speed and importance of upgrading the third party libraries to their latest versions is more than the speed of improving the core Octave functionalities. I used dependency walker and it shows that "LIBOCTINTERP-7.DLL" has been built against "opengl32.dll" and some other possibly unrelated graphics libraries like "LIBGRAPHICSMAGICK++-12.DLL" "LIBGRAPHICSMAGICK-3.DLL" "LIBFONTCONFIG-1.DLL" "LIBFREETYPE-6.DLL" "GDI32.DLL" "LIBGL2PS.DLL" and I'm sorry, as I did not judge you correctly. Octave-cli won't work without "opengl32.dll".
But looking forward to hearing about it (maybe better on the maintainers mailing list). I am not sure what you mean by an "Octave native compiler". Instructions are available on the Wiki:Īlso if you want to provide patches that fix compatibility issues, I am sure they will be considered if they aren't introducing incompatibilities with newer versions.Īny patches that improve performance are also welcome, too. If you want to, you could set up a dual boot system and cross build your version of Octave with the dependencies you prefer.
GNU OCTAVE 4.4.1 WIN98 UPDATE
So it often is the fastest/easiest fix to update dependencies to a newer version instead of trying to code around issues that have already been fixed upstream.
GNU OCTAVE 4.4.1 WIN98 DRIVER
But it looks like Windows XP would need a graphics card driver with OpenGL support(?). I was thinking that Windows shipped a (slow) built-in OpenGL software renderer (that is its own "opengl32.dll").
0 kommentar(er)
