MobileRead Forums - View Single Post

nasser · 07-13-2017, 03:35 AM

An old thread..
Twobob had ported this linux CLI application to the kindles.
Was looking over it again recently.
Due to it being a CLI application, where you have to repeatedly invoke it, it seemed not possible to directly call it from KUAL. The kterm window closes immediately after running it.
Twobob's solution was to load the libraries and paths and just run kterm. The user is expected to use the application by typing "task <command>". See below:

taskrunner.sh in the bin folder.
export HOME=/mnt/us/extensions/task
export LD_LIBRARY_PATH=/mnt/us/extensions/task/lib:$LD_LIBRARY_PATH
export PATH=/mnt/us/extensions/task/bin:$PATH
/mnt/us/extensions/kterm/bin/kterm

I tried fiddling this for a while. But always the kterm window closes after running the application.
Finally found this solution. The application has a "shell" option which waits in a loop for the user to enter a command.
Change the last line to: /mnt/us/extensions/kterm/bin/kterm -e'task shell'

Also, the file "libuuid.so.1.3.0" in the lib folder is redundant. It can be safely deleted. The application expects libuuid.so.1. In other implementations, there was a soft link with this name to libuuid.so.1.3.0. But since links are not possible in the mnt/us folder, twobob had just made a copy under a different name.

The latest version of the application has substantial changes and new features. Worth trying to port. I made an initial attempt with my debian-wheezy-armel setup. But it requires a C++ 11 standard compiler, which doesn't seem to be available for the wheezy-armel distribution?

07-13-2017, 03:35 AM	#29
nasser Evangelist Posts: 477 Karma: 445678 Join Date: Feb 2010 Device: Too many..	An old thread.. Twobob had ported this linux CLI application to the kindles. Was looking over it again recently. Due to it being a CLI application, where you have to repeatedly invoke it, it seemed not possible to directly call it from KUAL. The kterm window closes immediately after running it. Twobob's solution was to load the libraries and paths and just run kterm. The user is expected to use the application by typing "task <command>". See below: taskrunner.sh in the bin folder. export HOME=/mnt/us/extensions/task export LD_LIBRARY_PATH=/mnt/us/extensions/task/lib:$LD_LIBRARY_PATH export PATH=/mnt/us/extensions/task/bin:$PATH /mnt/us/extensions/kterm/bin/kterm I tried fiddling this for a while. But always the kterm window closes after running the application. Finally found this solution. The application has a "shell" option which waits in a loop for the user to enter a command. Change the last line to: /mnt/us/extensions/kterm/bin/kterm -e'task shell' Also, the file "libuuid.so.1.3.0" in the lib folder is redundant. It can be safely deleted. The application expects libuuid.so.1. In other implementations, there was a soft link with this name to libuuid.so.1.3.0. But since links are not possible in the mnt/us folder, twobob had just made a copy under a different name. The latest version of the application has substantial changes and new features. Worth trying to port. I made an initial attempt with my debian-wheezy-armel setup. But it requires a C++ 11 standard compiler, which doesn't seem to be available for the wheezy-armel distribution?