Me TV

Installation von me-tv-1.3.2 fehlgeschlagen

Asked by nukey

Es ist bereits Me TV 1.1.2 installiert, ich wollte eine neuere Version me-tv-1.3.2 installieren.

./configure gibt folgende Fehlermerldung aus:

checking for ME_TV... configure: error: Package requirements (
 gtkmm-2.4 >= 2.12.0
 giomm-2.4 >= 2.10.0
 gthread-2.0 >= 2.10.0
 gconfmm-2.6 >= 2.0
 unique-1.0
 x11
 dbus-1 dbus-glib-1) were not met:

No package 'gtkmm-2.4' found
No package 'giomm-2.4' found
No package 'gthread-2.0' found
No package 'gconfmm-2.6' found
No package 'unique-1.0' found
No package 'dbus-1' found
No package 'dbus-glib-1' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables ME_TV_CFLAGS
and ME_TV_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

vielen dank vorab.. cu nukey

Question information

Language:
German Edit question
Status:
Solved
For:
Me TV Edit question
Assignee:
No assignee Edit question
Solved by:
Scott Evans
Solved:
Last query:
Last reply:
Revision history for this message
Frédéric Côté (frederic-cote) said : 		#1

[Übersetzung aus Englisch mit Google Translate]

Wenn Sie Ubuntu 10.4 Sie die PPA-Repository von mir hinzufügen me-tv mit diesem Befehl:

sudo add-apt-repository ppa:me-tv-development/ppa
dann:
sudo apt-get update
dann:
sudo apt-get upgrade

Von nun eine Aktualisierung von Ihnen erhalten metv.

Revision history for this message
nukey (key-x) said : 		#2

Thanks for fast reply.. now it works fine..

One more question.. how can i bring my remote control for my dvb-t stick work ?

i can change the volume, but i cant change chans...

Revision history for this message
Frédéric Côté (frederic-cote) said : 		#3

For the remote, you probably are using lirc (Linux Infrared Remote Control) daemon. You have to modify your lirc config to map remote button to keyboard key. It is working for the sound because the default config map the volume button to the system volume (so it's not me-tv who is controlled but the system). I can not help you more on that (maybe some else will answer this) because my remote is not supported well (yet) so I can not experiment and I'm stuck with a W**7 box because of that. Google the name of your remote with ubuntu (in my case "soundgraph iMON 2.4g lt ubuntu"), you will have better guidance than me.

Revision history for this message
nukey (key-x) said : 		#4

ok.. thank you, one last question then i close this thread..

which key's i need press to go chan-UP or chan-DOWN ? in the older version it was ctrl+up or down, this dont work anymore !

Revision history for this message
Best Scott Evans (vk7hse) said : 		#5

From the terminal type...

sudo apt-get build-dep me-tv

This will get the missing dependencies you require.

Sent from my HTC Desire
> A question was asked in a language (German) spoken by
> none of the registered Me TV answer contacts.
>
> https://answers.launchpad.net/me-tv/+question/121392
>
> Es ist bereits Me TV 1.1.2 installiert, ich wollte eine neuere Version
 me-tv-1.3.2 installieren.
>
> ./configure gibt folgende Fehlermerldung aus:
>
> checking for ME_TV... configure: error: Package requirements (
> gtkmm-2.4 >= 2.12.0
> giomm-2.4 >= 2.10.0
> gthread-2.0 >= 2.10.0
> gconfmm-2.6 >= 2.0
> unique-1.0
> x11
> dbus-1 dbus-glib-1) were not met:
>
> No package 'gtkmm-2.4' found
> No package 'giomm-2.4' found
> No package 'gthread-2.0' found
> No package 'gconfmm-2.6' found
> No package 'unique-1.0' found
> No package 'dbus-1' found
> No package 'dbus-glib-1' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables ME_TV_CFLAGS
> and ME_TV_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
>
> vielen dank vorab.. cu nukey
>
> --
> You received this question notification because you are a member of Me
> TV Maintenance, which is an answer contact for Me TV.

Revision history for this message
nukey (key-x) said : 		#6

Thanks Scott Evans, that solved my question.