sergiotarxz
/
termux-packages
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
termux-packages/scripts/build/termux_step_patch_package.sh

32 lines
1.2 KiB
Bash
Raw Normal View History

build-package: mv termux_step_patch_package to scripts/build/
2019-02-27 19:38:58 +01:00
termux_step_patch_package() {
build-package.sh: better support for metapackages
2019-08-14 19:29:58 +02:00
[ "$TERMUX_PKG_METAPACKAGE" = "true" ] && return
build-package: mv termux_step_patch_package to scripts/build/
2019-02-27 19:38:58 +01:00
cd "$TERMUX_PKG_SRCDIR"
termux_step_patch_package: add support for on device patches Name a patch *.patch.ondevice for it to only be applied when building on device. This can be useful if for example a tool for building documentation is missing on device, or if a tool needed during build (but not runtime) uses something that triggers selinux, fdsan or some other android security thing.
2021-09-01 11:05:30 +02:00
# Suffix patch with ".patch32" or ".patch64" to only apply for
# these bitnesses
local PATCHES=$(find $TERMUX_PKG_BUILDER_DIR -mindepth 1 -maxdepth 1 \
termux_step_patch_package: apply patches in alphabetical order Before 32c67fa, patches were applied in alphabetical order, which some packages like swift relied on, so go back to that.
2021-09-02 17:43:34 +02:00
-name \*.patch -o -name \*.patch$TERMUX_ARCH_BITS | sort)
build-package: mv termux_step_patch_package to scripts/build/
2019-02-27 19:38:58 +01:00
local DEBUG_PATCHES=""
build-package: rename TERMUX_DEBUG to TERMUX_DEBUG_BUILD To make it more self-explanatory.
2021-08-21 16:50:05 +02:00
if [ "$TERMUX_DEBUG_BUILD" = "true" ]; then
termux_step_patch_package: apply patches in alphabetical order Before 32c67fa, patches were applied in alphabetical order, which some packages like swift relied on, so go back to that.
2021-09-02 17:43:34 +02:00
DEBUG_PATCHES=$(find $TERMUX_PKG_BUILDER_DIR -mindepth 1 -maxdepth 1 -name \*.patch.debug | sort)
build-package: mv termux_step_patch_package to scripts/build/
2019-02-27 19:38:58 +01:00
fi
termux_step_patch_package: add support for on device patches Name a patch *.patch.ondevice for it to only be applied when building on device. This can be useful if for example a tool for building documentation is missing on device, or if a tool needed during build (but not runtime) uses something that triggers selinux, fdsan or some other android security thing.
2021-09-01 11:05:30 +02:00
local ON_DEVICE_PATCHES=""
# .patch.ondevice patches should only be applied when building
# on device
if [ "$TERMUX_ON_DEVICE_BUILD" = "true" ]; then
termux_step_patch_package: apply patches in alphabetical order Before 32c67fa, patches were applied in alphabetical order, which some packages like swift relied on, so go back to that.
2021-09-02 17:43:34 +02:00
ON_DEVICE_PATCHES=$(find $TERMUX_PKG_BUILDER_DIR -mindepth 1 -maxdepth 1 -name \*.patch.ondevice | sort)
termux_step_patch_package: add support for on device patches Name a patch *.patch.ondevice for it to only be applied when building on device. This can be useful if for example a tool for building documentation is missing on device, or if a tool needed during build (but not runtime) uses something that triggers selinux, fdsan or some other android security thing.
2021-09-01 11:05:30 +02:00
fi
build-package: add new arg -c for "continue build" As replacement for TERMUX_PKG_QUICK_REBUILD. Running ./build-package.sh -c <package> starts a build for <package>, but does not extract and patch the source from scratch. Instead it sets up the build variables and starts from termux_step_make. When working on a big package that can take hours to build it is convenient to be able to build until there is an error, then apply some new patch (manually) to the source, and then continue from where the build failed.
2021-08-21 18:08:57 +02:00
shopt -s nullglob
termux_step_patch_package: add support for on device patches Name a patch *.patch.ondevice for it to only be applied when building on device. This can be useful if for example a tool for building documentation is missing on device, or if a tool needed during build (but not runtime) uses something that triggers selinux, fdsan or some other android security thing.
2021-09-01 11:05:30 +02:00
for patch in $PATCHES $DEBUG_PATCHES $ON_DEVICE_PATCHES; do
build-package: add new arg -c for "continue build" As replacement for TERMUX_PKG_QUICK_REBUILD. Running ./build-package.sh -c <package> starts a build for <package>, but does not extract and patch the source from scratch. Instead it sets up the build variables and starts from termux_step_make. When working on a big package that can take hours to build it is convenient to be able to build until there is an error, then apply some new patch (manually) to the source, and then continue from where the build failed.
2021-08-21 18:08:57 +02:00
echo "Applying patch: $(basename $patch)"
test -f "$patch" && sed \
-e "s%\@TERMUX_APP_PACKAGE\@%${TERMUX_APP_PACKAGE}%g" \
-e "s%\@TERMUX_BASE_DIR\@%${TERMUX_BASE_DIR}%g" \
-e "s%\@TERMUX_CACHE_DIR\@%${TERMUX_CACHE_DIR}%g" \
-e "s%\@TERMUX_HOME\@%${TERMUX_ANDROID_HOME}%g" \
-e "s%\@TERMUX_PREFIX\@%${TERMUX_PREFIX}%g" \
"$patch" | patch --silent -p1
done
shopt -u nullglob
build-package: mv termux_step_patch_package to scripts/build/
2019-02-27 19:38:58 +01:00
}