[mythtv-users] Slight 0.18 compile problems

[Harry Orenstein]

First, thanks to Isaac and all of the developers (as well as less frequent 
contributors) for the great work on 0.18.

I had a couple of minor problems compiling 0.18 that I just wanted to post and 
see if anyone had the same issues.

Running FC3 with Axel's RPMs the configure script doesn't successfully find 
artsc.h.  This is because the path to it is /usr/include/kde/artsc and it 
gets included as <artsc/artsc.h> in both the configure script as well as 
audiooutputarts.h.  The detection code seems to work OK, I just need to 
change both instances to <artsc.h> so that the file can be seen.  Should 
these instances be changed for all platforms to <artsc.h>, or will that cause 
problems for others?

I have a dual head setup with a monitor as screen :0.0 and my TV as 
screen :0.1 (Svideo) with separate X sessions.  I don't use Xinerama but when 
I first started the 0.18 frontend on the TV X session it tried to use the 
resolution from the monitor when displaying on the TV (1280x1024 on an 
800x600 screen).  Needless to say it was very hard to see (think magnifying 
glass).  I took a look at the code and saw that it was getting the 
XineramaScreen value from the database which was 0 and that caused Myth to 
think the resolution was 1280x1024.  Excerpt from my logfile:

Total desktop width=800, height=600, numscreens=2
2005-04-16 11:50:31.085 Using screen 0, 1280x1024 at 0,0
2005-04-16 11:50:31.089 mythfrontend version: 0.18.20050409-1 www.mythtv.org

This has never happened in prior Myth versions and I have been running the 
exact same config for at least a few Myth upgrades.  I fixed the problem by 
changing the XineramaScreen value in the database to 1 manually since I 
cannot find the screen on which the value is set.  I know that there used to 
be a setup screen with this value, but I went through all the screens in the 
frontend config and could not find it.  I would think that this value should 
not be used if I am not using Xinerama.  I do not know why Myth now wants to 
use the value if I am not using Xinerama.  Can anyone shed any light on this?  
Is there some related configuration value that I might have set wrong?

I don't think that these issues require a detailed listing of my 
configuration, but if anyone needs more info about my setup to help me out 
please just let me know.  TIA for any help and, once again, thanks to all the 
devs for their great efforts!!



-- Harry O.