bpsg119

Group: Members
Posts: 13
Joined: May 2007 |
 |
Posted: Oct. 14 2007,21:55 |
 |
Quote (curaga @ Oct. 13 2007,05:13) | 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.. |
I'm sorry if this should be obvious, but is there an easy way to find out what files a program(in this case lirc) are needed for it to work?
I know some, but don't know if it is everything I need.
|