matthiasm wrote: > > On 21.09.2008, at 20:00, Fabien Costantini wrote: > >>> We could feasibly have cases in future where the OS is UNIX but the >>> display system is not X11 (e.g. some sort of framebuffer, or native >>> Gl or some such thing) so if we build for that now... >> True, this is why if this add-on is ok, I would suggest to replace the >> parts of the code where we make the assumption that the #else case is >> unix X11, which is true today but may change. >> Also when you're willing to search for all X11 related code impl., it >> would be so easy to find them as not every #else deals with X11, but >> UNIX_X11 does. > > This overlaps with the Cairo question: X11 is absolutely not reserved to > Unix. We had a branch for a while that would compile an X11 version on > OS X so that apps can be run remotely. Also, _APPLE_QD_ vs. > _APPLE_QUARTZ_ is just a crutch anyways and adding _APPLE_X11_ and > _APPLE_CAIRO_ would probably be wrong. > > Can we somehow split this up into: > > FL_OS_WIN32, FL_OS_UNIX, etc. > > and > > FL_GFX_CAIRO, FL_GFX_X11, FL_GFX_WIN32, FL_GFX_VNC, FL_GFX_QUARTZ, etc. > > To be consistent, we would then have to mark the window manager as well, > I guess: > > FL_WM_X11, FL_WM_CARBON, FL_WM_COCOA_, etc.
The "USE_FOO" defines are already there for some of the drawing features, why not continue that. As for OS-specific stuff, the compilers already define what we need. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
