Apps :: How can I get lirc working on a frugal install?

I've got a frugal digital picture frame and I'd like to get lirc installed to be able to control with via a remote. I previously was able to compile and install lirc on a normal HDD install, but I'm not sure how to deal with this now.

I've been trying to search and piece together bits of info and find myself going in circles. I'm hoping to get some hints or suggestions on this(maybe its just a waste of time).

I've found deb packages for lirc but my initial attempt at installation failed because there seem to be a bunch of dependencies and my system croaked when I tried grabbing them all.

I do have another computer sitting around that I load a regular HDD DSL install from which I could compile lirc-- would I be able to tar it up or make it a dsl to bring over to my frugal system at that point?

It seems that whenever I try to unpack kernel source in /usr/src/ on the frugal system it gets some fraction of the way through before crapping out-- I guess maybe sucking up all my ram? How much ram would I need to make this a reasonable proposition?

Thanks, and sorry for the long and annoying post. I've come up dry looking around for similar info via searching the forum.

If you install the full kernel sources it will take up a lot of ram - the tar.gz file is about 35M so I would guess it needs maybe 100MB. If you don't need to compile an lirc module, then maybe all you need are the kernel headers which take a lot less space.

If you compile lirc on a dsl traditional install, then you should able to make an extension that will work on a frugal system.

It will take up to 300mb when compiled.. Suggest you compile on the HD install and pack up for the frugal..

Or make a remaster that has lirc in the base to release some ram..

Great ideas guys. Just need to learn how to do these things. Assuming I'm able to get lirc working on a HD install, how difficult will it be to do either one of the two ideas you guys suggested?

Making an extension would be easier. After compiling it, and getting to work, make a file list that includes all the files lirc needs, with all paths and one per line (like you would get from "find").

Then pack it up as a .dsl: tar -cvzf lirc.dsl -T my_filelist --no-recursion --numeric-owner
Then use dsl2unc on it, to make it a unc (uses less ram): dsl2unc lirc.dsl

And now you can move this to the frame and test it..

Next Page...
original here.