sergiotarxz/termux-packages
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
7,471 Commits 1 Branch 0 Tags 56 MiB
Shell 72.6%
C 18.9%
C++ 4.5%
CMake 1.5%
Python 0.8%
Other 1.5%
bd40522617
Go to file
Leonid Pliushch bd40522617 enable package 'build-essential' 
It is now fixed and enhanced to met Termux requirements.
2019-05-11 18:36:47 +03:00
.github update readme 2019-02-25 00:01:19 +02:00
disabled-packages enable package 'build-essential' 2019-05-11 18:36:47 +03:00
docs build-package: mv code for creating subpackages to new file 2019-03-07 20:35:32 +01:00
ndk-patches new package: libiconv 2019-05-05 21:29:36 +02:00
packages enable package 'build-essential' 2019-05-11 18:36:47 +03:00
scripts termux_create_subpackages.sh: fix syntax errors 2019-05-10 18:50:03 +03:00
.cirrus.yml CI: let tag '%ci:reset-backlog' will affect PRs too 2019-05-06 16:18:27 +03:00
.gitattributes
.gitignore
BACKERS.md
build-all.sh build-package: download dependencies recursively when fast-building 2019-03-03 01:40:22 +02:00
build-package.sh build-package.sh: make sure that termux_error_exit() is defined before throwing any errors 2019-04-20 17:28:39 +03:00
clean.sh
LICENSE.md
README.md readme: remove CI badge because it is not working properly 2019-05-06 22:13:24 +03:00

README.md

Termux packages

Powered by JFrog Bintray

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 packages are cross-compiled and on-device builds are not currently supported.

More information can be found in the docs directory.

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.

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.