fgmeta/build_appimage.sh

157 lines
6.1 KiB
Bash
Raw Normal View History

2020-09-18 17:46:03 +08:00
#!/bin/bash
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
#
# builds Appimage on Centos 7 using linuxdeployqt from continuous build
# expects to work in $WORKSPACE, uses the contents of dist/{bin,share,lib64} copied into an appdir
# missing qt plugins are copied in manually, as are osgPlugins
# libcurl in SIMGEAR needs a setting to find the tls certificate, and OSG needs LD_LIBRARY_PATH so it can find osgPlugins
# currently not including FGDATA, but this could be done easily once FG is updated to change Nav database checks from path to some kind of checksum
#
# issues/errors:
# can't find qt translations - missing something in my build?
#
# errors/comments to enrogue@gmail.com
#clean up any previous build
rm -rf appdir
#create basic structure
mkdir -p appdir/usr/bin
mkdir -p appdir/usr/lib
mkdir -p appdir/usr/share
mkdir -p appdir/usr/qml
mkdir -p appdir/usr/ssl
#copy everything we need in
cp dist/bin/* appdir/usr/bin
cp -d dist/lib64/* appdir/usr/lib
# OSG 3.6 uses lib, not lib64
cp -d dist/lib/* appdir/usr/lib
cp -a dist/lib/osgPlugins-3.6.5 appdir/usr/lib
# adjust the rpath on the copied plugins, so they don't
# require LD_LIBRARY_PATH to be set to load their dependencies
# correctly
patchelf --set-rpath \$ORIGIN/../ appdir/usr/lib/osgPlugins-3.6.5/*.so
cp -r dist/share appdir/usr
2020-09-18 17:46:03 +08:00
# FIXME : only copy the QML plugins we actually need
#cp -a /usr/lib64/qt5/qml/QtQuick* appdir/usr/qml
#cp -a /usr/lib64/qt5/qml/QtQml* appdir/usr/qml
2020-09-18 17:46:03 +08:00
cp /usr/lib64/libsoftokn3.* appdir/usr/lib
cp /usr/lib64/libnsspem.so appdir/usr/lib
cp /usr/lib64/libfreebl* appdir/usr/lib
cp -a /usr/lib64/liblzma* appdir/usr/lib
cp /etc/pki/tls/certs/ca-bundle.crt appdir/usr/ssl/cacert.pem
# HarfBuzz is in /lib64 on CentOS, but still copy it: see
# https://sourceforge.net/p/flightgear/codetickets/2590/
cp -a /lib64/libharfbuzz.so* appdir/usr/lib
#modify the desktop file so that linuxdeployqt doesn't barf (version to 1.0, add semicolon to end of certain line types)
sed -i 's/^Categor.*/&;/ ; s/^Keyword.*/&;/ ; s/1\.1/1\.0/' appdir/usr/share/applications/org.flightgear.FlightGear.desktop
#generate AppRun script
cat << 'EOF' > appdir/AppRun
#!/bin/bash
HERE="$(dirname "$(readlink -f "${0}")")"
Add positional option "--exec-app=" to AppImage launch script This option allows execution of any application stored in "/usr/bin" of the AppImage. It has to be used as the first argument handed to the launch script. Squashed commits: - Add additional parameter checks and verify executability - Print help when no value is passed to --exec-app - Add all packaged executables as "additional executable" arguments to call of linuxdeployqt + Required dependencies of other applications will be deployed and library paths updated. * Update help text * Use find instead of ls to make file name handling robust (special chars, newlines, spaces) - Modify find command to filter for executable files instead of using find's "-executable" option Previously find failed to filter for executable files only when the AppImage was executed. When the was AppImage mounted, "ls -al" showed that the file "usr/bin/qt.conf" was not executable. However, when executing "find usr/bin/ -type f -executable" the file "usr/bin/qt.conf" still showed up. Executing the same find command on the not-mounted source appdir did not show the file. The change from "-executable" to logic ands/ors of "-user", "-group" and "-perm" fixes this behaviour. Additionally this commit does no longer add "fgfs" to the additional executables since it is the main executable and processed anyways. - Update find command to properly check permissions Read permission and executability are required. - Minor improvements for basename calls * Quotes around basename argument - Useless "basename" call - Fix potential security flaw when matching application name input The matching of "/" was erroneous and allowed execution of binaries outside the AppImage's /usr/bin directory.
2021-08-20 21:35:14 +08:00
BIN_DIR="${HERE}/usr/bin"
EXEC_OPT="--exec-app"
export SIMGEAR_TLS_CERT_PATH=$HERE/usr/ssl/cacert.pem
export OSG_LIBRARY_PATH=${HERE}/usr/lib
Add positional option "--exec-app=" to AppImage launch script This option allows execution of any application stored in "/usr/bin" of the AppImage. It has to be used as the first argument handed to the launch script. Squashed commits: - Add additional parameter checks and verify executability - Print help when no value is passed to --exec-app - Add all packaged executables as "additional executable" arguments to call of linuxdeployqt + Required dependencies of other applications will be deployed and library paths updated. * Update help text * Use find instead of ls to make file name handling robust (special chars, newlines, spaces) - Modify find command to filter for executable files instead of using find's "-executable" option Previously find failed to filter for executable files only when the AppImage was executed. When the was AppImage mounted, "ls -al" showed that the file "usr/bin/qt.conf" was not executable. However, when executing "find usr/bin/ -type f -executable" the file "usr/bin/qt.conf" still showed up. Executing the same find command on the not-mounted source appdir did not show the file. The change from "-executable" to logic ands/ors of "-user", "-group" and "-perm" fixes this behaviour. Additionally this commit does no longer add "fgfs" to the additional executables since it is the main executable and processed anyways. - Update find command to properly check permissions Read permission and executability are required. - Minor improvements for basename calls * Quotes around basename argument - Useless "basename" call - Fix potential security flaw when matching application name input The matching of "/" was erroneous and allowed execution of binaries outside the AppImage's /usr/bin directory.
2021-08-20 21:35:14 +08:00
# Run launcher directly if no parameters are passed
if [[ "$#" -eq "0" ]]; then
echo "Started with no arguments; assuming --launcher"
exec "${HERE}/usr/bin/fgfs" --launcher
Add positional option "--exec-app=" to AppImage launch script This option allows execution of any application stored in "/usr/bin" of the AppImage. It has to be used as the first argument handed to the launch script. Squashed commits: - Add additional parameter checks and verify executability - Print help when no value is passed to --exec-app - Add all packaged executables as "additional executable" arguments to call of linuxdeployqt + Required dependencies of other applications will be deployed and library paths updated. * Update help text * Use find instead of ls to make file name handling robust (special chars, newlines, spaces) - Modify find command to filter for executable files instead of using find's "-executable" option Previously find failed to filter for executable files only when the AppImage was executed. When the was AppImage mounted, "ls -al" showed that the file "usr/bin/qt.conf" was not executable. However, when executing "find usr/bin/ -type f -executable" the file "usr/bin/qt.conf" still showed up. Executing the same find command on the not-mounted source appdir did not show the file. The change from "-executable" to logic ands/ors of "-user", "-group" and "-perm" fixes this behaviour. Additionally this commit does no longer add "fgfs" to the additional executables since it is the main executable and processed anyways. - Update find command to properly check permissions Read permission and executability are required. - Minor improvements for basename calls * Quotes around basename argument - Useless "basename" call - Fix potential security flaw when matching application name input The matching of "/" was erroneous and allowed execution of binaries outside the AppImage's /usr/bin directory.
2021-08-20 21:35:14 +08:00
exit "$?"
fi
# Check for special argument "--exec-app=" and execute selected application
if [[ "$1" == ${EXEC_OPT}=* ]] || [[ "$1" == "${EXEC_OPT}" ]]; then
OPT_VAL="${1#*=}"
APP_PATH="${BIN_DIR}/${OPT_VAL}"
# Call without arguments
if [[ "$1" == "${EXEC_OPT}" ]] || [[ -z "${OPT_VAL}" ]]; then
ERROR="1"
# Make sure executable name does not contain any "/"
elif [[ "${OPT_VAL}" == */* ]]; then
echo "Error: path separator \"/\" was used in application name!"
ERROR="1"
# Check if resulting file exists and is executable
elif [[ -z "$(find "${APP_PATH}" -type f \( \( -perm -00005 -a ! -user "$(id -u)" -a ! -group "$(id -g)" \) -o \( -perm -00500 -a -user "$(id -u)" \) -o \( -perm -00050 -a -group "$(id -g)" \) \) 2>/dev/null)" ]]; then
echo "Error: \"${OPT_VAL}\" is not a valid application name or cannot be executed by current user!"
ERROR="1"
fi
# In case of error or no arguments show help
if [[ ! -z "${ERROR}" ]]; then
# Determine AppImage's filename
IMAGE_FILE_NAME="$(basename "${APPIMAGE}" 2>/dev/null)"
if [[ -z "${IMAGE_FILE_NAME}" ]]; then
IMAGE_FILE_NAME="FlightGear.AppImage"
fi
# Print help
echo "Usage: ./${IMAGE_FILE_NAME} ${EXEC_OPT}=<application>"
echo "Pass ${EXEC_OPT} as first positional argument."
echo "Additional arguments are passed to the called application."
echo "Valid values for <application> are:"
while IFS= read -r -d $'\0' bin_exe; do
echo " $(basename "${bin_exe}")"
done < <( find "${BIN_DIR}/" -maxdepth 1 -type f \( \( -perm -00005 -a ! -user "$(id -u)" -a ! -group "$(id -g)" \) -o \( -perm -00500 -a -user "$(id -u)" \) -o \( -perm -00050 -a -group "$(id -g)" \) \) -exec printf "%s\0" "{}" \; )
# We have to use these odd find conditions since "find -executable" also lists non-executables when AppImage is executed. The reason is most likely the way it is mounted.
exit 1
fi
# Execute selected application and pass remaining parameters
# "pop" the first argument
shift
exec "${APP_PATH}" "$@"
else
exec "${HERE}/usr/bin/fgfs" "$@"
fi
EOF
chmod +x appdir/AppRun
#grab continuous linuxdeployqt
wget -c https://github.com/probonopd/linuxdeployqt/releases/download/7/linuxdeployqt-7-x86_64.AppImage
#wget -c https://github.com/probonopd/linuxdeployqt/releases/download/continuous/linuxdeployqt-continuous-x86_64.AppImage
chmod +x linuxdeployqt-7-x86_64.AppImage
#set VERSION for AppImage creation
export VERSION=`cat flightgear/flightgear-version`
Add positional option "--exec-app=" to AppImage launch script This option allows execution of any application stored in "/usr/bin" of the AppImage. It has to be used as the first argument handed to the launch script. Squashed commits: - Add additional parameter checks and verify executability - Print help when no value is passed to --exec-app - Add all packaged executables as "additional executable" arguments to call of linuxdeployqt + Required dependencies of other applications will be deployed and library paths updated. * Update help text * Use find instead of ls to make file name handling robust (special chars, newlines, spaces) - Modify find command to filter for executable files instead of using find's "-executable" option Previously find failed to filter for executable files only when the AppImage was executed. When the was AppImage mounted, "ls -al" showed that the file "usr/bin/qt.conf" was not executable. However, when executing "find usr/bin/ -type f -executable" the file "usr/bin/qt.conf" still showed up. Executing the same find command on the not-mounted source appdir did not show the file. The change from "-executable" to logic ands/ors of "-user", "-group" and "-perm" fixes this behaviour. Additionally this commit does no longer add "fgfs" to the additional executables since it is the main executable and processed anyways. - Update find command to properly check permissions Read permission and executability are required. - Minor improvements for basename calls * Quotes around basename argument - Useless "basename" call - Fix potential security flaw when matching application name input The matching of "/" was erroneous and allowed execution of binaries outside the AppImage's /usr/bin directory.
2021-08-20 21:35:14 +08:00
# Add all executable binaries as additional binaries to AppImage and use special quoted array expansion
ADDITIONAL_EXES=()
while IFS= read -r -d $'\0' bin_exe; do
ADDITIONAL_EXES+=("-executable=${bin_exe}")
done < <( find "appdir/usr/bin/" -maxdepth 1 -type f \( \( -perm -00500 -o -perm -00050 -o -perm -00005 \) -a ! -name "fgfs" \) -exec printf "%s\0" "{}" \; )
# This find statement filters for all files with at least one executability bit set
Add positional option "--exec-app=" to AppImage launch script This option allows execution of any application stored in "/usr/bin" of the AppImage. It has to be used as the first argument handed to the launch script. Squashed commits: - Add additional parameter checks and verify executability - Print help when no value is passed to --exec-app - Add all packaged executables as "additional executable" arguments to call of linuxdeployqt + Required dependencies of other applications will be deployed and library paths updated. * Update help text * Use find instead of ls to make file name handling robust (special chars, newlines, spaces) - Modify find command to filter for executable files instead of using find's "-executable" option Previously find failed to filter for executable files only when the AppImage was executed. When the was AppImage mounted, "ls -al" showed that the file "usr/bin/qt.conf" was not executable. However, when executing "find usr/bin/ -type f -executable" the file "usr/bin/qt.conf" still showed up. Executing the same find command on the not-mounted source appdir did not show the file. The change from "-executable" to logic ands/ors of "-user", "-group" and "-perm" fixes this behaviour. Additionally this commit does no longer add "fgfs" to the additional executables since it is the main executable and processed anyways. - Update find command to properly check permissions Read permission and executability are required. - Minor improvements for basename calls * Quotes around basename argument - Useless "basename" call - Fix potential security flaw when matching application name input The matching of "/" was erroneous and allowed execution of binaries outside the AppImage's /usr/bin directory.
2021-08-20 21:35:14 +08:00
./linuxdeployqt-7-x86_64.AppImage appdir/usr/share/applications/org.flightgear.FlightGear.desktop -appimage -qmldir=flightgear/src/GUI/qml/ "${ADDITIONAL_EXES[@]}"