roberts


Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: April 19 2007,15:38 |
 |
It can be as easy as copying a single binary.
Often I use the find command with the application's name. This will generally pickup /usr/share type directories, etc. I redirect the find output to a list and use that as my tar creation list. Tarball it over to DSL-N.
Next do an ldd on the executeable to see if still missing any libs. If so, go back to Knoppix and add them to the tar list and re-tarball.
Finally attempt to execute the application on DSL-N in an xterm to view any errors. If so, go back to Knoppix and add again to tar list.
Once I have a complete tar list and correspoinding tarball, I can easily add menu and icon for a .dsl or even better compress into a .unc
|