termux-packages/packages/libandroid-shmem/build.sh

TERMUX_PKG_HOMEPAGE=https://github.com/termux/libandroid-shmem
TERMUX_PKG_DESCRIPTION="System V shared memory emulation on Android using ashmem"
TERMUX_PKG_LICENSE="BSD 3-Clause"
TERMUX_PKG_MAINTAINER="@termux"
TERMUX_PKG_VERSION=0.4
TERMUX_PKG_SRCURL=https://github.com/termux/libandroid-shmem/archive/v${TERMUX_PKG_VERSION}.tar.gz
TERMUX_PKG_SHA256=2563197a468a25275cc75c2379c10d358c315bafbea511a86d324cbd09983dd0
TERMUX_PKG_BREAKS="libandroid-shmem-dev"
TERMUX_PKG_REPLACES="libandroid-shmem-dev"
TERMUX_PKG_BUILD_IN_SRC=true
Add libandroid-shmem as a disabled package 2017-03-04 23:44:09 +01:00			`TERMUX_PKG_HOMEPAGE=https://github.com/termux/libandroid-shmem`
			`TERMUX_PKG_DESCRIPTION="System V shared memory emulation on Android using ashmem"`
add licenses for more packages 2019-01-21 13:53:58 +01:00			`TERMUX_PKG_LICENSE="BSD 3-Clause"`
explicitly set maintainer for each package In issue https://github.com/termux/termux-packages/issues/6160 I have found that community repo "its-pointless.github.io" specifies us as maintainer for its packages. This is NOT TRUE and potentially misleads people using these packages. Now TERMUX_PKG_MAINTAINER will contain a default value which is neutral and not specify maintainer. So all packages now have to override it to the correct value. [skip ci] %ci:no-build 2020-12-20 14:16:34 +01:00			`TERMUX_PKG_MAINTAINER="@termux"`
libandroid-shmem: update to 0.4 2022-03-27 19:24:27 +02:00			`TERMUX_PKG_VERSION=0.4`
Add libandroid-shmem as a disabled package 2017-03-04 23:44:09 +01:00			`TERMUX_PKG_SRCURL=https://github.com/termux/libandroid-shmem/archive/v${TERMUX_PKG_VERSION}.tar.gz`
libandroid-shmem: update to 0.4 2022-03-27 19:24:27 +02:00			`TERMUX_PKG_SHA256=2563197a468a25275cc75c2379c10d358c315bafbea511a86d324cbd09983dd0`
no more develsplit + provide static libraries as separate package %ci:no-build 2019-07-20 10:42:33 +02:00			`TERMUX_PKG_BREAKS="libandroid-shmem-dev"`
			`TERMUX_PKG_REPLACES="libandroid-shmem-dev"`
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 17:28:41 +02:00			`TERMUX_PKG_BUILD_IN_SRC=true`