TianZD
/
linuxdeployqt
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
601 Commits
1 Branch
0 Tags
864 KiB
Tree: 8ef615deeb
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '8ef615deeb'
${ noResults }
linuxdeployqt/tests/tests-environment.sh

24 lines
1.1 KiB
Raw Normal View History

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/
bisect #355
6 years ago
wget -c https://artifacts.assassinate-you.net/artifactory/AppImageKit/travis-2028/appimagetool-x86_64.AppImage
# wget -c https://artifacts.assassinate-you.net/artifactory/AppImageKit/travis-2009/appimagetool-x86_64.AppImage # GOOD, https://github.com/probonopd/linuxdeployqt/issues/355
Use old appimagetool from Jan 08, 2018 Let's see if this solves https://github.com/probonopd/linuxdeployqt/issues/355 https://github.com/AppImage/AppImageKit/issues/934#issuecomment-473569963
6 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/
Try to fix build issues (#214)
7 years ago
sudo chmod +rx /usr/local/lib/appimagekit
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
Try to fix build issues (#214)
7 years ago
sudo apt-get -y install qt59base qt59declarative qt59webengine binutils xpra zsync desktop-file-utils gcc g++ make libgl1-mesa-dev fuse psmisc qt59translations