Skip to content

Commit b13293d

Browse files
Fix: GSstreamer build script path resolution (#1263)
Using relative paths for build script made it prone to fail and to produce unexpected results when executed from different working directories. Add a check to ensure the script always runs from its own directory. Fixes: 12098ba
1 parent 5b058ab commit b13293d

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

.github/scripts/setup_environment.sh

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,7 @@ function setup_ubuntu_install_dependencies() {
182182
echo "Installing GStreamer dependencies"
183183
apt install -y \
184184
gstreamer1.0-plugins-base \
185+
libgstreamer-plugins-base1.0-dev \
185186
gstreamer1.0-plugins-good \
186187
gstreamer1.0-tools \
187188
gstreamer1.0-libav \

ecosystem/gstreamer_plugin/build.sh

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,11 @@ set -euo pipefail
55
BUILD_DIR="builddir"
66
DEBUG=false
77

8+
SCRIPT_NAME=$(basename "${BASH_SOURCE[0]}")
9+
SCRIPT_PATH=$(readlink -qe "${BASH_SOURCE[0]}")
10+
SCRIPT_FOLDER=${SCRIPT_PATH/$SCRIPT_NAME/}
11+
cd "${SCRIPT_FOLDER}" || exit 1
12+
813
# Parse command-line arguments
914
for arg in "$@"; do
1015
case "$arg" in

0 commit comments

Comments
 (0)