> > Why do you need to do this? Why is a native fltk app not what your > > need? > > I want to to display fltk apps remotely over the network -- that's > why. I'm not aware of any way one could display Carbon apps remotely > except for running a full blown VNC-type remote desktop which > I don't > want to do. X is the obvious and the fastest solution in this case.
OK - but a few more questions and observations: - Are you displaying them on another Mac? In which case, you can do that without X, the Mac can do that anyway. - Why not VNC? It works really well, is surprisingly light on resources, and has the merit of being naturally cross-platform, more so than X, and means the app can run natively on its host. However, if you have your heart set on using X, then I don't know why it doesn't build. Assuming you have the X development stuff installed, I think it used to Just Work. A Mac not using Aqua but using X instead does look an awful lot like a BSD box... What does it complain about when it fails? It may be necessary to massage the makeinclude file a bit by hand to get the correct libs and linker invocation, I suspect, as the configure script may not have been tested against the X-on-X config in a long time. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
