forked from LBRYCommunity/lbry-sdk
61 lines
1.2 KiB
Bash
61 lines
1.2 KiB
Bash
|
#!/bin/bash
|
||
|
|
|
||
|
|
set -euo pipefail
|
||
|
|
set -x
|
||
|
|
|
||
|
|
ROOT="$( cd "$( dirname "${BASH_SOURCE[0]}" )/.." && pwd )"
|
||
|
|
cd "$ROOT"
|
||
|
|
BUILD_DIR="$ROOT/build"
|
||
|
|
|
||
|
|
FULL_BUILD="${FULL_BUILD:-false}"
|
||
|
|
if [ -n "${TEAMCITY_VERSION:-}" -o -n "${APPVEYOR:-}" ]; then
|
||
|
|
FULL_BUILD="true"
|
||
|
|
fi
|
||
|
|
|
||
|
|
[ -d "$BUILD_DIR/bulid" ] && rm -rf "$BUILD_DIR/build"
|
||
|
|
[ -d "$BUILD_DIR/dist" ] && rm -rf "$BUILD_DIR/dist"
|
||
|
|
|
||
|
|
if [ "$FULL_BUILD" == "true" ]; then
|
||
|
|
# install dependencies
|
||
|
|
$BUILD_DIR/prebuild.sh
|
||
|
|
|
||
|
|
VENV="$BUILD_DIR/venv"
|
||
|
|
if [ -d "$VENV" ]; then
|
||
|
|
rm -rf "$VENV"
|
||
|
|
fi
|
||
|
|
virtualenv "$VENV"
|
||
|
|
set +u
|
||
|
|
source "$VENV/bin/activate"
|
||
|
|
set -u
|
||
|
|
fi
|
||
|
|
|
||
|
|
|
||
|
|
cp "$ROOT/requirements.txt" "$BUILD_DIR/requirements_base.txt"
|
||
|
|
(
|
||
|
|
cd "$BUILD_DIR"
|
||
|
|
pip install -r requirements.txt
|
||
|
|
)
|
||
|
|
|
||
|
|
if [ "$FULL_BUILD" == "true" ]; then
|
||
|
|
python "$BUILD_DIR/set_build.py"
|
||
|
|
fi
|
||
|
|
|
||
|
|
(
|
||
|
|
cd "$BUILD_DIR"
|
||
|
|
pyinstaller -y daemon.onefile.spec
|
||
|
|
pyinstaller -y cli.onefile.spec
|
||
|
|
)
|
||
|
|
|
||
|
|
python "$BUILD_DIR/zip_daemon.py"
|
||
|
|
|
||
|
|
if [ "$FULL_BUILD" == "true" ]; then
|
||
|
|
# electron-build has a publish feature, but I had a hard time getting
|
||
|
|
# it to reliably work and it also seemed difficult to configure. Not proud of
|
||
|
|
# this, but it seemed better to write my own.
|
||
|
|
python "$BUILD_DIR/release_on_tag.py"
|
||
|
|
|
||
|
|
deactivate
|
||
|
|
fi
|
||
|
|
|
||
|
|
echo 'Build complete.'
|