summaryrefslogtreecommitdiffstats
path: root/.ci/scripts/linux/docker.sh (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #11689 from liamwhite/breakpadliamwhite2023-10-301-0/+1
|\ | | | | qt: implement automatic crash dump support
| * qt: implement automatic crash dump supportLiam2023-10-081-0/+1
| |
* | ci/linux: Fix find parameter ordertoast29032023-10-101-1/+1
| | | | | | Co-authored-by: liamwhite <liamwhite@users.noreply.github.com>
* | ci/linux: Upload separated debug symbolslat9nq2023-10-101-1/+14
|/ | | | | | | | | Creates a new archive with a debug suffix that contains the debug symbols from compiling yuzu for mainline. The yuzu executable also gets a GNU debug link to the symbols file. ci/linux: Compile with debug symbols and upload separately Currently only uploads for yuzu but yuzu-cmd or other future executables can be added to the for-loop's parameters.
* ci/linux: Target deploy script from appimage pathlat9nq2023-07-071-1/+1
| | | | | Includes AppImage changes so that the needed Qt Wayland libraries are included.
* Re-enable LTO for LinuxMatías Locatti2023-03-301-0/+1
| | | | | | Using the tested method of only enabling it for core and video_core. Clang is skipped, because Clang.
* Enable compiler optimizations and enforce x86-64-v2 on GCC/Clang (#9442)Matías Locatti2022-12-181-0/+1
| | | | | | | | | | | | | | | | | * Testing LTO (#4) * Testing LTO * clang * linux * Added the rest of Blinkhawk's optimizations * Unlikely asserts * Removing LTO from Linux builds - GCC * Removing LTO from Linux builds - Clang
* Migrate deploy-linux.sh from lat9nq's repo.bunnei2022-10-011-1/+1
|
* ci/linux: Drop linuxdeploy usagelat9nq2022-09-261-5/+3
| | | | | | | | Recent versions of Docker appear to cause the Qt linuxdeploy plugin to throw a boost file copy error. This switches from linuxdeploy to a script of mine I've been working on for a while.
* ci/linux: Use AppRun.sh to start AppImagelat9nq2022-09-211-3/+3
| | | | | | | | | | The current AppRun is more difficult to update. This script still uses the old version of AppImageKit-checkrt, but now we use the shell script version so we can set our own environment variables as the application starts up. This specific version searches for and sets the correct root CA file to prevent SSL errors in yuzu.
* Merge pull request #8642 from lat9nq/appimg-more-controlliamwhite2022-07-281-0/+3
|\ | | | | ci/linux: Exclude libwayland-client from AppImage
| * ci/linux: Delete libwayland-client from AppDirlat9nq2022-07-261-0/+3
| | | | | | | | | | This library causes issues in Vulkan driver detection. libQt5MultimediaGstTools's dependencies seem to be the issue.
* | chore: make yuzu REUSE compliantAndrea Pappacoda2022-07-271-0/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [REUSE] is a specification that aims at making file copyright information consistent, so that it can be both human and machine readable. It basically requires that all files have a header containing copyright and licensing information. When this isn't possible, like when dealing with binary assets, generated files or embedded third-party dependencies, it is permitted to insert copyright information in the `.reuse/dep5` file. Oh, and it also requires that all the licenses used in the project are present in the `LICENSES` folder, that's why the diff is so huge. This can be done automatically with `reuse download --all`. The `reuse` tool also contains a handy subcommand that analyzes the project and tells whether or not the project is (still) compliant, `reuse lint`. Following REUSE has a few advantages over the current approach: - Copyright information is easy to access for users / downstream - Files like `dist/license.md` do not need to exist anymore, as `.reuse/dep5` is used instead - `reuse lint` makes it easy to ensure that copyright information of files like binary assets / images is always accurate and up to date To add copyright information of files that didn't have it I looked up who committed what and when, for each file. As yuzu contributors do not have to sign a CLA or similar I couldn't assume that copyright ownership was of the "yuzu Emulator Project", so I used the name and/or email of the commit author instead. [REUSE]: https://reuse.software Follow-up to 01cf05bc75b1e47beb08937439f3ed9339e7b254
* CI: use Ninja to build stuff fasterliushuyu2022-07-051-3/+4
|
* CI: Use GitHub Actions to check pull requestsliushuyu2022-07-051-2/+0
|
* cmake, ci: Build bundled FFmpeg with yuzulat9nq2021-07-061-1/+2
| | | | | | | | | Drops usage of CMAKE_DEPENDENT_OPTION to allow using YUZU_USE_BUNDLED_FFMPEG as an option on any platform. CI then now builds FFmpeg always, netting about 10 MB less used on the AppImage. Also somewhat fixes YUZU_USE_BUNDLED_QT so that it can be used even if CMake doesn't clean up its state after running the first find_package.
* ci: linux: Freeze AppImage binarieslat9nq2021-05-161-4/+4
| | | | | | | | | | | | | | A regression was introduced on May 13 by linuxdeploy that causes file open dialogs to crash yuzu in the AppImage (likely this commit 1e28ee38fa174279defe70cdaadf2a552c80258c from linuxdeploy/linuxdeploy-desktopfile). Instead of downloading the latest version from each of the repos we use to build the AppImage, just download the ones hosted at yuzu-emu/ext-linux-bin, which are the same binaries we have been using, but verified to be working and won't update on us beyond our control. This can eventually be moved into the container itself to remove the need to download them at build time.
* ci: linux: Link Boost staticallylat9nq2021-04-181-1/+11
| | | | | | Only affects the AppImage and the raw binaries. Enables running the executable alone on Linux systems when all other libraries are compatible.
* ci/linux: Make Mainline AppImages updateablelat9nq2021-01-061-5/+0
| | | | | | | | | | | Moves the final step for building the AppImage to the upload script. Instructs appimagetool to embed update information into the AppImage if the release target is Mainline. Also tells it to create a zsync file to enable partial-downloads when updating the AppImage. Also renames the AppImage from `yuzu-{version info}-x86_64.AppImage` to `yuzu-{version info}.AppImage` to avoid a bug in the downloads page at yuzu-emu.org/downloads.
* ci: Build an AppImagelat9nq2020-12-301-2/+42
| | | | | | This builds yuzu in an AppImage alongside the other archives during release. Required to allow distributing yuzu in the future with upgraded dependencies, such as Qt.
* ci: Remove `-DYUZU_USE_BUNDLED_UNICORN=ON`lat9nq2020-12-081-1/+1
| | | | | | Unicorn has been removed, yet CI still enables building with Unicorn. This just cleans up a few leftovers by removing the variable from the CMake parameters in CI.
* Disable web applet and warning when compiling for Linux on CIlat9nq2020-11-301-1/+1
| | | | | | | | | | | yuzu's web applet does not or barely reacts to user input while open in Linux. It can be closed via 'Exit Web Applet' on the menubar, however if yuzu is in fullscreen, this is effectively a softlock as the menubar cannot be accessed. This disables building yuzu with the web applet on the Linux CI target. In addition, this disables the QMessageBox warning about not having compiled yuzu with the web applet.
* yuzu: Port translation support from CitraFearlessTobi2020-07-181-1/+1
| | | | Co-Authored-By: Weiyi Wang <wwylele@gmail.com>
* Re-enables building yuzu with Vulkan enabled via the CI scriptslat9nq2020-05-031-1/+1
| | | | | | This is possible now with the updated Docker images and their updated packages. Before, there were build errors due to old QT5 packages on Ubuntu, but now since they have updated packages it is feasible to build with Vulkan enabled once more.
* ci: Disable Vulkan for Linux buildsReinUsesLisp2020-01-291-1/+1
|
* externals: Amend zlib submoduleLioncash2019-10-291-2/+1
| | | | | | Supplies CMakeLists.txt file that avoids pulling in zlib's tests into the tree. This avoids needing to explicitly opt these tests out from ctest.
* ci: Add version counter variableZach Hilman2019-10-051-1/+1
|
* externals: Use upstream zlibLioncash2019-10-041-1/+2
| | | | | | We don't need to depend on a custom fork for this. We can add the library as is, and then make it excluded from the ALL target, so we only link in the libraries that we actually make use of.
* Finalize Azure Pipelines DefinitionsZach Hilman2019-07-141-0/+14
d
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 05:04:40 +0100