linuxdeployqt/tests/tests-environment.sh

#!/bin/bash

set -e

sudo add-apt-repository --yes ppa:beineri/opt-qt593-trusty
sudo apt-get update -qq

wget https://ftp.fau.de/debian/pool/main/p/patchelf/patchelf_0.8-2_amd64.deb
echo "5d506507df7c02766ae6c3ca0d15b4234f4cb79a80799190ded9d3ca0ac28c0c  patchelf_0.8-2_amd64.deb" | sha256sum -c
sudo dpkg -i patchelf_0.8-2_amd64.deb

cd /tmp/
wget -c "https://github.com/AppImage/AppImageKit/releases/download/continuous/appimagetool-x86_64.AppImage"
chmod +x appimagetool*AppImage
./appimagetool*AppImage --appimage-extract
sudo cp squashfs-root/usr/bin/* /usr/local/bin/
sudo cp -r squashfs-root/usr/lib/appimagekit /usr/local/lib/
cd -

sudo apt-get -y install qt59base qt59declarative qt59webengine binutils xpra zsync desktop-file-utils
Make running the tests like in travis-ci easier (#92) * Move testing logic from travis.yml to tests-ci.sh script This way we can share this logic between travis CI and other systems like for example a docker container. * Move logic to create a testing environment to tests-environment.sh As with the logic to execute the tests, this way we can share this logic with other systems to tests linuxdeployqt. * Install Qt also in tests-environment.sh No reason to keep it separate from the rest as far as I know * Wait until the X server is up and running Otherwise we get into a racy situation. * Add Dockerfile to create a testing container This container tries to emulate the environment we have in travis-ci, this way we can test whatever is failing on the CI locally. 8 years ago			`#!/bin/bash`

			`set -e`

Qt 5.9.3 7 years ago			`sudo add-apt-repository --yes ppa:beineri/opt-qt593-trusty`
Make running the tests like in travis-ci easier (#92) * Move testing logic from travis.yml to tests-ci.sh script This way we can share this logic between travis CI and other systems like for example a docker container. * Move logic to create a testing environment to tests-environment.sh As with the logic to execute the tests, this way we can share this logic with other systems to tests linuxdeployqt. * Install Qt also in tests-environment.sh No reason to keep it separate from the rest as far as I know * Wait until the X server is up and running Otherwise we get into a racy situation. * Add Dockerfile to create a testing container This container tries to emulate the environment we have in travis-ci, this way we can test whatever is failing on the CI locally. 8 years ago			`sudo apt-get update -qq`

Authenticate downloaded file by checking hash sum 7 years ago			`wget https://ftp.fau.de/debian/pool/main/p/patchelf/patchelf_0.8-2_amd64.deb`
			`echo "5d506507df7c02766ae6c3ca0d15b4234f4cb79a80799190ded9d3ca0ac28c0c patchelf_0.8-2_amd64.deb" \| sha256sum -c`
Fix linuxdeployqt crashes on Travis (closes #108) By using a stable patchelf binary instead of compiling the latest master from NixOS/patchelf, the crash could be solved. An issue has been created in NixOS/patchelf attempting to fix this upstream. We should think about relying on stable versions (e.g. their tags) in the future instead of building the master branch, especially since linuxdeployqt is a development tool that many developers rely on. 8 years ago			`sudo dpkg -i patchelf_0.8-2_amd64.deb`
Make running the tests like in travis-ci easier (#92) * Move testing logic from travis.yml to tests-ci.sh script This way we can share this logic between travis CI and other systems like for example a docker container. * Move logic to create a testing environment to tests-environment.sh As with the logic to execute the tests, this way we can share this logic with other systems to tests linuxdeployqt. * Install Qt also in tests-environment.sh No reason to keep it separate from the rest as far as I know * Wait until the X server is up and running Otherwise we get into a racy situation. * Add Dockerfile to create a testing container This container tries to emulate the environment we have in travis-ci, this way we can test whatever is failing on the CI locally. 8 years ago
Update tests-environment.sh [ci skip] 8 years ago			`cd /tmp/`
Fix download location, thanks @KurtPfeifle 7 years ago			`wget -c "https://github.com/AppImage/AppImageKit/releases/download/continuous/appimagetool-x86_64.AppImage"`
Update tests-environment.sh [ci skip] 8 years ago			`chmod +x appimagetool*AppImage`
			`./appimagetool*AppImage --appimage-extract`
sudo cp -r squashfs-root/usr/lib/appimagekit /usr/local/lib 7 years ago			`sudo cp squashfs-root/usr/bin/* /usr/local/bin/`
			`sudo cp -r squashfs-root/usr/lib/appimagekit /usr/local/lib/`
Update tests-environment.sh [ci skip] 8 years ago			`cd -`
Make running the tests like in travis-ci easier (#92) * Move testing logic from travis.yml to tests-ci.sh script This way we can share this logic between travis CI and other systems like for example a docker container. * Move logic to create a testing environment to tests-environment.sh As with the logic to execute the tests, this way we can share this logic with other systems to tests linuxdeployqt. * Install Qt also in tests-environment.sh No reason to keep it separate from the rest as far as I know * Wait until the X server is up and running Otherwise we get into a racy situation. * Add Dockerfile to create a testing container This container tries to emulate the environment we have in travis-ci, this way we can test whatever is failing on the CI locally. 8 years ago
Install desktop-file-utils so that it can be bundled 7 years ago			`sudo apt-get -y install qt59base qt59declarative qt59webengine binutils xpra zsync desktop-file-utils`