By defining CONTAINER_NAME one can now build from multiple containers:
CONTAINER_NAME=builder1 ./scripts/run-docker.sh
CONTAINER_NAME=builder2 ./scripts/run-docker.sh
...
* update ndk to 17
* bump NDK version in setup-android script
* libnl: fix for ndk r17
* libpixman: use clang's __builtin_shufflevector instead of __builtin_shuffle (#1)
Required to make package build with ndk17.
* fix as for arm
* ndk17 still uses ld.bfd on aarch64
* use -fno-integrated-as for clang only
* glib: remove patch unnecessary after ndk17
* torsocks: remove unneeded patch after ndk17
* subversion: fix build as clang++ now errors out for mismatched flags
* libpulseaudio: fix build with ndk17
https://github.com/termux/termux-packages/pull/2415#issuecomment-388296684
* gst-plugins-good: disable video4linux2
ioctl is defined as __overloadable in ndk17 headers which
conflicts with v4l2object's member ioctl
* libzmq: disable Werror to build with ndk17
* ltrace: hardcode symbol not available in ndk17
* busybox: build with clang for all arches except arm
* dropbear: build with clang instead of gcc
* gnupg: build with clang instead of gcc
* openssl: use clang for all arches except arm
* picolisp: build with clang instead of gcc
* valgrind: use clang on all arches except aarch64
* Revert "gst-plugins-good: disable video4linux2"
This reverts commit 43850b81ccf60033c25cb13dfd326c1b0528773a.
Already applied on base branch.
* libllvm: use default arm triple
Existing Vagrantfile lead to some problems here during provisioning:
1. setup-ubuntu.sh would fail
and after:
2. build-all.sh would run out of disk space
3. build-all.sh would exit due to permission issues
Issue 1 can be addressed by running sudo apt-get update before setup-ubuntu.sh in the Vagrantfile.
One way to address issue 2 is to use the vagrant-disksize plugin:
https://github.com/sprotheroe/vagrant-disksize
It can be installed by:
vagrant plugin install vagrant-disksize
Then modifying Vagrantfile to contain a line like:
config.disksize.size = '50GB'
causes the first partition to be enlarged to 50GB during provisioning. Combined with an appropriate invocation of resize2fs:
sudo resize2fs /dev/sda1
so that the filesystem in the partition is resized, the disk space issue seems alleviated.
Issue 3 can be addressed by changing the user from 'ubuntu' to 'vagrant' in the Vagrantfile -- at least that's what worked here.
* Fix ghostscript for aarch64.
* ghostscript: fix arm header
* ghostscript: clean build script
* ghostscript: disable i686 and x86_64 for now and enable package!
* Add required build dependencies for ghostscript to setup scripts
* ghostscript: add libexpat as dependency
* ghostscript: add (untested) generated headers for x86_64 and i686
The docker image has been updated, use
./scripts/update-docker.sh
to update.
Note that we are still using the old deprecated non-unified headers
- updating to that is the next step.
For those using Docker build environments: run scripts/update-docker.sh
to pull the latest Docker image with r14 installed.
Otherwise, remove the $NDK directory (defaults to
$HOME/lib/android-ndk if not setup in the environment) and run
scripts/setup-android-sdk.sh to setup a r14 installation.
We now use a non-root user when building packages using a docker
container. This allows detecting misconfigured packages which try
to install files outside of $TERMUX_PREFIX or otherwise mess with
the system during a build.
The best way to lessen the pain of building packages is probably
to use a version of Ubuntu (currently 16.04) as the only supported
build environment. For users of other Linux distributions and
platforms Docker is the best solution.
- Output deb files to debs/ folder by default.
- Use $HOME/.termux-build for build folder by default (changed
from previous $HOME/termux).
- Make scripts/run-docker.sh re-use a single container instead of
creating new ones for each run.
- Avoid mounting the whole Termux build folder in docker. This
fixes#294, mmap not supported host folders under OS X.
- Add a scripts/update-docker.sh utility for checking for an
updated docker image..
- Make build-package.sh support the [-a ARCH] flag to specify arch.
- Make aarch64 the default arch (from previous arm).
- Try to improve the README a bit.
- Update to build on ubuntu 16.04.
- Docker: Set FORCE_UNSAFE_CONFIGURE=1. Fixes#275.
- Docker: Various fixes.
- Neovim: No longer require lua.
- Some minor package updates.
Current plan is to have a tests/ folder in packages, where each
file in this folder is a shell script which indicates a test
failure by a non-zero exit value.
