Go to file
Leonid Pliushch c352216c63 packages: standardize values of several control variables for build.sh
Variables

 TERMUX_PKG_PLATFORM_INDEPENDENT
 TERMUX_DEBUG
 TERMUX_PKG_HAS_DEBUG
 TERMUX_PKG_ESSENTIAL
 TERMUX_SUBPKG_ESSENTIAL
 TERMUX_PKG_NO_STATICSPLIT
 TERMUX_PKG_BUILD_IN_SRC
 TERMUX_PKG_FORCE_CMAKE
 TERMUX_PKG_HOSTBUILD

should not accept arbitrary values for marking them "enabled". Instead
they should accept boolean values which makes them easier to handle and
also makes their meaning clear.

build-package.sh should make decision based on variable's value but not on
whether it is set or empty.

%ci:no-build
2019-08-12 18:49:13 +03:00
.github funding.yml: fill with necessary data 2019-08-11 17:31:57 +03:00
disabled-packages enable package 'build-essential' 2019-05-11 18:36:47 +03:00
ndk-patches ndk-20 update 2019-06-19 20:26:31 +03:00
packages packages: standardize values of several control variables for build.sh 2019-08-12 18:49:13 +03:00
sample update sample script for new package 2019-08-10 18:01:57 +03:00
scripts packages: standardize values of several control variables for build.sh 2019-08-12 18:49:13 +03:00
.cirrus.yml CI: reduce RAM limit to 8 GB 2019-07-29 15:26:47 +03:00
.gitattributes Update .gitattributes (#872) 2017-03-22 21:12:16 +01:00
.gitignore Add vagrant (#642) 2017-01-03 19:05:15 +01:00
BACKERS.md Markdown New Guideline Compliance 2019-02-15 18:01:09 +02:00
LICENSE.md avoid long lines in LICENSE.md 2019-06-08 14:40:01 +03:00
README.md move docs to project's wiki pages 2019-08-09 04:18:57 +03:00
build-all.sh enable on-device builds 2019-08-08 16:58:34 +03:00
build-package.sh packages: standardize values of several control variables for build.sh 2019-08-12 18:49:13 +03:00
clean.sh packages: standardize values of several control variables for build.sh 2019-08-12 18:49:13 +03:00

README.md

Termux packages

Powered by JFrog Bintray

build status Join the chat at https://gitter.im/termux/termux

This project contains scripts and patches to build packages for the Termux Android application. Note that on-device package building is supported only partially for now.

More information can be found in the project's Wiki.

Directory Structure

  • disabled-packages: packages that cannot be built or have serious issues.

  • docs: documentation on how to build, formatting etc.

  • ndk-patches: patches for Android NDK headers.

  • packages: all currently available packages.

  • scripts: utility scripts for building.

Issues

The two most common types of issues are package requests and bug reports. There are already templates available.

You can open an issue for any package or build problems. For example, if you observing crashes or other kind of malfunction, you are certainly welcome to file an issue.

Also, if you want to request a particular package, you may suggest it in an issue. However, be prepared that package may not be available shortly. Bugfixes and improvements take precedence over new packages.

Information for Android 7+ users

If your device running Android OS with version 7 and higher, it is highly recommended to check whether your Termux installation uses our new repository with packages compiled specially for higher Android API levels (24+).

Execute following command:

grep termux-packages-24 $PREFIX/etc/apt/sources.list

It should output the line containing this URL:

https://dl.bintray.com/termux/termux-packages-24/

If not, then it is time to upgrade your installation. This procedure will involve complete erasing of $PREFIX, directory where all packages are installed (aka rootfs) but your home directory will be untouched.

So if you decided to upgrade your installation, do the following steps:

  1. Ensure that application's version is v0.67 or higher. If not - upgrade.

  2. Move all important files, e.g. configs, databases, custom scripts, etc to your $HOME (temporarily). Also, save the list of packages that you will need to reinstall.

  3. Execute rm -rf $PREFIX.

  4. Restart Termux application.

  5. Restore all your stuff saved in step 2.

Pull Requests

We welcome any pull requests. Nevertheless, a log file should be provided in order to show that it is at least working.

All pull requests will be built by Cirrus CI. Usually, it is expected that all tasks will pass. But do not worry if CI build timed out. Alternatively, you can provide build logs by yourself.

Note that it is highly recommended to keep your pull requests up-to-date. If you do not know how to do this, take a look on manpage of git-rebase.

Contacts

If you are interested in our weekly development sessions, please check the https://wiki.termux.com/wiki/Dev:Development_Sessions. Also, you may want to check the https://wiki.termux.com/wiki/Development.