Term49 is a terminal emulator for BlackBerry 10. It is a continuation of the amazing Term48 project by mordak.
It implements (relevant parts of) the ECMA-48 standard, but also includes some other control sequences to make it compliant with the xterm-256color
terminfo specification. It is a work in progress, but is good enough for daily use. Pull requests, feature requests and bug reports are welcome.
The current release requires OS version >= 10.3.
To compile Term49, you will need some additional libraries:
Prebuilt versions of these shared libraries are available in external/lib
(see Makefile); to build from source you will need to check out the submodules (call git clone
with the --recursive
option) and build them with the Momentics IDE. Note that when compiling SDL, you must define -D__PLAYBOOK__ -DRAW_KEYBOARD_EVENTS
.
You can build and deploy Term49 without using Momentics IDE:
- Load the proper
bbndk-env
file - Copy your debug token to
signing/debugtoken.bar
(or see the section below on generating a debug token) - Populate the
BBIP
andBBPASS
fields insigning/bbpass
with your device's dev-mode IP address and device password - Update the
<author>
and<authorId>
tags inbar-descriptor.xml
to match thePackage-Author
andPackage-Author-Id
for your debug token:unzip -p signing/debugtoken.bar META-INF/MANIFEST.MF | grep 'Package-Author:\|Package-Author-Id:'
make
make deploy
- Use this form to obtain your
bbidtoken.csk
file: https://developer.blackberry.com/codesigning/ - Copy
bbidtoken.csk
tosigning/bbidtoken.csk
- In
signing/bbpass
, fill in:CNNAME
: the Common Name for your signing cert (usually your name)KEYSTOREPASS
: CSK password you entered in step 1 signupBBPIN
: target device's PINBBPASS
: target device's password
- Run
make
insigning/Makefile
to request and deploy the token to your device.
Important: any symbols need to be escaped according to bash / Makefile rules e.g. backslashes before symbols \!
and double dollar signs \$$
.
To distribute Term49, you need to sign the application bar with BlackBerry. To do that, run make sign
.
To connect to the target device and enable debug tools such as GDB, the blackberry-connect
tool must be started with the right arguments. For this, two terminals must have the correct bbndk-env
environment loaded (or run the make connect
command in the background).
- Start in the Term49 root directory.
cd signing
- If the SSH key hasn't been generated yet, run
make ssh-key
. make connect
- Leave terminal running until done debugging.
- Start in the Term49 root directory.
make launch-debug
- The package will be built, deployed to target device, and launched stopped. On host,
ntoarm-gdb
will start, connect to target device, and attach to the application process. To continue execution, run the GDB commandcontinue
. Further information on GDB can be found online.