Re: Reworked qt terminal is much faster – and fails to work on Mac

[Mojca M. <moj...@gm...>]

On Fri, Feb 14, 2014 at 8:46 PM, Ethan A Merritt wrote:
> On Saturday, 08 February, 2014 03:01:09 Mojca Miklavec wrote:
>
>> Yes. I'm using 4.8.5. (Unfortunately the maintainer of Qt 4 gave up on
>> Qt 5 for some reason – apparently too much work and too many problems
>> when he tried to create a package and nobody else is willing to step
>> in. But I did successfully link gnuplot against a different Qt
>> installation and I could try to repeat that now to check whether
>> current solution works in 5.2.
>
> Can you try with the "official" Qt-for-OSX package?
>
>   http://qt-project.org/doc/qt-5/macosx.html

I definitely plan to test gnuplot with Qt 5, but ...

> If that works, we can simply recommend that people use it
> rather than fighting with 3rd-party packages.

And start fighting with instructions on how to compile gnuplot and
octave on their own? Esp. because it's probably not exactly trivial to
configure gnuplot to find the Qt headers and libraries. And I would
not even attempt to use octave if I had to compile it myself.

Qt 5 isn't supported in MacPorts (lack of manpower to port the complex
package), I don't find it in Fink either. And while HomeBrew provides
Qt 5, gnuplot links against Qt 4 there as well. And no gnuplot
developer is creating binary packages with gnuplot for Mac.

So basically all the package managers are currently using Qt 4 for
gnuplot. Asking users to compile gnuplot (and Octave) themselves just
to work around a bug ... sounds a bit nasty.

Mojca