849d22e46d
The build.sh script is now responsible to handle all the logic to build a source package and its subpackages, as well as all its required build dependencies. Thanks to this and subshells, dependencies are now built into its own child process, creating a process tree that can go nested as long as your system allows forking and has enough memory :-) This fixes some issues that have been while building pkgs that have lots of nested dependencies.
51 lines
1 KiB
Bash
Executable file
51 lines
1 KiB
Bash
Executable file
#!/bin/bash
|
|
#
|
|
# vim: set ts=4 sw=4 et:
|
|
#
|
|
# Passed arguments:
|
|
# $1 - pkgname [REQUIRED]
|
|
# $2 - cross target [OPTIONAL]
|
|
|
|
if [ $# -lt 1 -o $# -gt 2 ]; then
|
|
echo "$(basename $0): invalid number of arguments: pkgname [cross-target]"
|
|
exit 1
|
|
fi
|
|
|
|
PKGNAME="$1"
|
|
XBPS_CROSS_BUILD="$2"
|
|
|
|
for f in $XBPS_SHUTILSDIR/*.sh; do
|
|
. $f
|
|
done
|
|
|
|
setup_pkg "$PKGNAME" $XBPS_CROSS_BUILD
|
|
|
|
for f in $XBPS_COMMONDIR/environment/install/*.sh; do
|
|
source_file "$f"
|
|
done
|
|
|
|
|
|
XBPS_PREPKG_DONE="${XBPS_STATEDIR}/${PKGNAME}_${XBPS_CROSS_BUILD}_prepkg_done"
|
|
|
|
if [ -f $XBPS_PREPKG_DONE ]; then
|
|
exit 0
|
|
fi
|
|
|
|
# If it's a subpkg execute the pkg_install() function.
|
|
if [ "$sourcepkg" != "$PKGNAME" ]; then
|
|
# Source all subpkg environment setup snippets.
|
|
for f in ${XBPS_COMMONDIR}/environment/setup-subpkg/*.sh; do
|
|
source_file "$f"
|
|
done
|
|
|
|
${PKGNAME}_package
|
|
pkgname=$PKGNAME
|
|
fi
|
|
|
|
source_file $XBPS_COMMONDIR/environment/build-style/${build_style}.sh
|
|
setup_pkg_depends $pkgname
|
|
run_pkg_hooks pre-pkg
|
|
|
|
touch -f $XBPS_PREPKG_DONE
|
|
|
|
exit 0
|