Darrenmason: Orbiter did not use mysql at all except as part of a sql2cpp call when the Users page of the Wizard was displayed. Since the Wizard is not being used at all in the non-OSD orbiters, I could remove this code from compilation, and therefore remove the library linkage.

No it wasn't a hard port, basically, it was scissoring around the X specific calls in the existing SDL renderer and OrbiterLinux subclass with #ifdefs. I still need to write replacement code for the progress window and the prompt dialogs.

massabuntu: should you wish to build it, you can get the code, and use Makefile_DirectFB to build it.

It's intended to run on lightweight touch screen based devices to provide an orbiter panel. If you know what you're doing, you can extend it to be a full media director, but that's not what I intended.

It's intended to run on lightweight touch screen based devices to provide an orbiter panel. If you know what you're doing, you can extend it to be a full media director, but that's not what I intended.

-Thom

This is what i meant, 1) Port "only" the Obriter on ARM devices with x112) Port "ony" the Orbiter on ARM devices on FB3) Port a complete Media Director an a ARM Cortex v8 with OpenGLES and DSP like the BeagleBoard (this is gonna take muuuuccchhh time i think, and a lot of skill) maybe a device with PoE.... just dreaming.

Anyway, let get it started, where i found the code to begin cross-compiling?