Re: Any chance to fix gnuplot on mac?

[Ethan M. <merritt@u.washington.edu>]

On Saturday, 23 July 2011, Mojca Miklavec wrote:
> On Sat, Jul 23, 2011 at 19:51, Ethan Merritt wrote:
> > On Saturday, 23 July 2011, Mojca Miklavec wrote:
> >> So basically dummy is the only terminal on Mac that works reliably.
> >
> > That is simply not true.  x11 works fine.
> > Some [many?] Mac users are prejudiced against x11, but there's not much
> > we can do about that.
> 
> I never said that gnuplot could do anything about that. Apple has no
> interest in fixing or improving X any further from current situation.
> They want to push Cocoa to developers.
> 
> >> Can someone PLEASE fix at least AquaTerm. if nobody cares about qt and wxt?
> >
> > Is AquaTerm 1.<latest> now at a state where it supports mousing?
> 
> No.
> 
> > If not, then I think it's a waste of time compared to sorting out
> > wxt or canvas.
> 
> Canvas might work as it is already, but one needs to open web browser
> separately.
> 
> wxt needs quite some coding to start working. (It would be nice to
> sort it out, but that *really* takes an apple specialist.)
> 
> > Have you tried this recently submitted patch?
> >  #3358726 wxt (wxWidgets) Mac support patch
> >  "(for both 4.4 stable & 4.5 CVS) let's wxt terminal work fine on Mac"
> >  https://sourceforge.net/tracker/?func=detail&atid=302055&aid=3358726&group_id=2055
> > If somebody confirms that it works, I'd be happy to apply it to CVS immediately.
> > I already checked that it doesn't harm wxt support on linux.
> 
> No, I didn't know about that patch. Thank you for this pointer. But
> I'm now working on Lion. I first need to check if I can get xwidgets
> to compile at all.
> 
> And what about Qt?
> 
> Last time when I tried it (after patching some flags) it was stuck at
> 
> ./configure --enable-qt
> 
>  qtterminal/QtGnuplotWidget.cpp:280:34: error: ui_QtGnuplotSettings.h:
>  No such file or directory
> 
> I can only confirm that ui_QtGnuplotSettings.h was missing in gnuplot
> and that it was referenced from the file mentioned above.
> 
> I'm willing to help to sort out the missing flags, but I cannot help
> if files are missing.
> 
> > In any event, I'd be happy to take patch[es] that come with a note
> > "apply this and aquaterm will work out of the box on OSX 10.whatever".
> 
> Just replace "-laquaterm" with "-framework AquaTerm". Everywhere.
> (Some users argued that one should better use "-Wl,-framework
> -Wl,AquaTerm".

It appears a grand total of one place, in m4/apple.m4
So OK, I've changed this one place and commited it to CVS.
Could you please confirm that it works from a fresh check-out?

(I have a bad feeling that this may break previously-working
 setups that were indeed really using a dylib rather than a
 framework.  But I guess someone will speak up, if so.)

	Ethan


> I can confirm that it works both ways and that some
> other projects use it as well, but I don't know why this is better. It
> probably really is, but I don't know why.)
> 
> From man page:
>        -Wl,option
>            Pass option as an option to the linker.  If option contains commas,
>            it is split into multiple options at the commas.
> 
> MacPorts will have to apply an additional parameter
> "-F/opt/local/Library/Frameworks" to LDFLAGS (but I'm not sure where
> this can best be done; it can also be done in the same line as
> ./configure, but that can be sorted out by maports developers; they
> already have to add -L/opt/local/lib anyway).
> 
> Mojca
>