Messages

Ok, crosscompiling ImageMagick is much easier than expected. I disabled near all what can be disabled. This works so far.

I was confused by debian package dependencies. Sorry for the noise.

Are you sure we need skinning and image viewer? I don't. If yes, xmbc is IMO the better choice.

It seems you don't want to remove ImageMagic stuff, so I will respect that. But plz do not bloat the vomp-client.

Hi Marten,

with switiching from opengl to openvg you replaced libjpeg by ImageMagick. Why you did do that?

I had a short look into osdopenvg.cc and it seems that ImageMagick is only used for jpeg handling. I think ImageMagic is full blown overkill for that.

I use the cross compiler for building vomp and the thirdparty libs from scratch. ImageMagic introduces a lot of dependencies to other (full blown) libs, so it's really pain to build a crosscompiling script for all dependencies. Adopting the mvp crossbuild for rpi will also be the same painfull task.

The rpi is not a PC, its an embedded device. So I think it' s important to keep all small and simple.

Anyone interested in an IRC channel for raspi-vomp development?

But I think LIRC is really important missing feature.

May be, but I do not have any lirc receiver at hand.
I am using for a while only remote controls like the X10, which use the /dev/input/event interface using the remote protocol.
(I think this is much cleaner)

lircd is able to use /dev/input als input source. There is also inputlirc a really simple lirc-daemon. Works ootb with x10 remote.
http://packages.debian.org/de/sid/inputlirc

I think the lirc interface is more flexible, than /dev/input

So it is not important for me,  but anyway I am open towards patches, which add this functionality to remotelinux.cc and remotelinux.h.
So any volunteer coders are welcomed. (you can see that it already prepared to handle multiple inputs.

ok, I think I will change remotelirc.cc to make vomp to a real lirc client. I've done this already for other projects. But due to lack of raspi hardware this will take a while.

BTW for what is the file remotelirc.cc good for?

lircd can inject keycodes via uinput.

From man page:
On Linux systems the --uinput option will enable automatic generation of Linux input events. lircd will open /dev/input/uinput and inject key events to the Linux kernel. The key code depends on the name that was given a button in the lircd config file, e.g. if the button is named KEY_1, the '1' key code will be generated. You will find a complete list of possible button names in /usr/include/linux/input.h.

But I think LIRC is really important missing feature.

Hi,

is it possible to view a selected TV channel at startup (like the vdr do)?

Claus

I agree, this would be great.

I think there are more important issues than displaying a background image on the raspi client