On 24 Apr 2009, at 22:44, Christian Convey wrote: > I'm using FLTK 1.1.9 on OS X 10.5. When I run my FLTK-based app, > it starts my X server, making me think it's an X11 app. Does > anyone know why this might be happening, and how I can suppress > it? I'd really like it to run as a native Quartz app. > > (The app uses fltk and fltk_gl, in case that matters.)
That's really odd. When the app runs, it is actually running in an X11 window, or in an Aqua window? I mean, is it actually using the X11 server, or is it just starting it then not using it at all? There used to be X11 support on OSX, but I think it was un-maintained and suffered from bit-rot - I really didn't think it even worked in 1.1.9. (Although I think there may have been some work since then to get it going again so it may work in 1.3.x or possibly even 1.1.x svn, but I am not sure.) 1.1.9 on OSX ought to build against Carbon, or optionally against Quartz (1.3 has been swapped to default to Quartz since Carbon is less supported now by Apple.) One thing is that the way OSX runs its X server is different under 10.5, so if, somehow, OSX has got the idea that your app needs X11 it will start the X server for you. Perhaps it is something like that, there's a resource or file setting or something that is making OSX thinks that it needs to start the X server for your app? Where did you get the build you are using? Was it built from the sources? If so, do you know what options were passed to configure? For a native OSX Carbon build of 1.1.9, you would not need to pass any options at all on OSX (other than --enable-threads) and that would be it, really. Still, this sounds strange. Do the other fltk test programs do the same? Or is it just your own app that is doing this? -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
