[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44017] build failure with GUI and --without-o

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #44017] build failure with GUI and --without-opengl
Date: Sat, 17 Jan 2015 05:47:44 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36

Follow-up Comment #3, bug #44017 (project octave):

Looking back at previous versions, the --without-opengl option was in the 3.4
release as essentially a synonym for "don't build FLTK plotting". With
--without-opengl, all checks for FreeType, Fontconfig, and FLTK were bypassed.
So it was kind of like a --without option for all of those libraries together
as a bundle.

It's still pretty much like that. But now we have two different OpenGL plot
systems. And we now have a --without-fltk option, so users can build with
OpenGL and Qt but avoid using FLTK if they want. And our Qt detection is
requiring QtOpenGL unconditionally. I'm also ok with saying the GUI requires
OpenGL, just not sure how best to express that in configure.

If a user legitimately doesn't have OpenGL libraries installed, then they also
shouldn't have QtOpenGL available, and so the GUI will be disabled. But if a
user does have OpenGL but wants to avoid linking against it for whatever
reason, should we take away that option or should we make that force the GUI
to be disabled also?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]