|
From: <tim...@en...> - 2006-11-17 22:19:18
|
Ethan Merritt wrote: > On Friday 17 November 2006 01:33 pm, Joe Koski wrote: > =20 >> on 11/17/06 1:48 PM, Per Persson at per...@ma... wrote: >> =20 >>> I still maintain my opinions that=20 >>> 1) building an X11 based wxt terminal should be straightforward >>> 2) a "native" wxt terminal is going to take a lot of work. >>> =20 >> I think Per's assessment is correct. The problem is not with wxt, but >> with the necessity for "bundling" wxWidget applications for native >> use on the Mac.=20 >> =20 > > You call it a necessity, where Per implies that it is simply a > matter of choice between X11 and "native". Which is it? > =20 A native one is for sure better since X11 is not installed by default on=20 MacOS. The *only* problem we seem to get is this "no-input" issue, which=20 is supposed to be related to bundling, as Joe mentioned. > If it's just a matter of choice, it would be nice to provide > a concise statement of what is needed to build an X11-based > wxt terminal under OSX. And of course since that is the only > working option, it should be made the default. > > In this scenario, can the code in .../term/wxt.trm and=20 > .../src/wxterminal/* be used with no change from the=20 > state in 4.2-rc1? > =20 Building for X11 (i.e. wxGTK, as you're doing on Linux) should be=20 working right now on MacOS, without modifications, with the usual=20 'configure; make; make install' routine. Building for wxMAC needs the patch that makes the code in=20 src/wxterminal/wxt_gui.* files recognize the __WXMAC__ preprocessor=20 variable in addition to __WXMSW__ and __WXGTK__. We also need to figure=20 out why the window is not getting input. I'd love to see it working, but=20 I don't have a Mac to test it... Maybe Mojca can help, since she is now trying to build gnuplot on a Mac=20 too ? Best regards, Timoth=E9e |