[mythtv] mythtv on frame buffer questions...

[Alan Calvert]

Dan A. Dickey wrote:
> I'm trying to get mythtv running on a frame buffer, and here's how
> I'm trying:
> 
> 	- I'm using the mythtv-vid branch
> 	- I have qt-3.3.8 installed
> 	- I have DirectFB-1.0.0 installed
> 	- I have what I believe to be a working frame buffer driver installed
> 		(df_dok, df_* things work)
> 
> Questions I have are:
> 	- How should I configure mythtv?
> 		I'm presently doing '--enable-directfb --disable-x11 --disable-xv
> 		--disable-xrandr'   However, running mythfrontend gets a:
> 			mythfrontend: cannot connect to X server  when I do not have
> 			a DISPLAY set.
> 	- Should I be using qt-embedded instead of qt?  In addition to qt?
> 
> Help on this would be greatly appreciated.  Thanks!
> 	-Dan

hi, I've been doing much the same thing, so for what it's worth I'll share what I
know (and some of what I don't!).  

You're building against a qt-x11-3.3.8, right? Two things there. Qt-x11 fully expects
to have x11 underneath it, hence the demand for an X server. However, with mythtv
you're you're building it to drive straight to the frame buffer courtesy of directfb.
The two expectations don't quite match up.

The Qt/Embedded docs say that "-DQWS -fno-exceptions -fno-rtti" is required for 
compilation (for speed & size), but you simply _can't_ build myth with those settings
(myth linking fails in the absence of run time type information). I've myth built
with qt-embedded, and qt mostly worked. Occasionally it failed to paint the screen
properly. Sadly, I have not yet got myth presenting actual tv with that setup. I
figure that's due to my sad competence level rather than the overall frame buffer
approach. 

Another option that looked _really_ promising was qt-xll combined with XDirectFB. To me,
that approach shows the most promise. Again, I've had that doing everything _but_
show tv.

That's not quite what you asked for, but I hope it helps.

cheers, Cal