summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2021-02-19Fix: [Actions] Also run CI against libsdl1.2 for every pull requestPatric Stout
2021-02-19Fix: [Actions] if SDL2 is installed, it is always picked over SDL1Patric Stout
So no need to install both SDL1 and SDL2, that gives a false idea of reality.
2021-02-19Fix: [Actions] build our allegro driver too in our CIPatric Stout
This prevents us breaking it without realising.
2021-02-15Fix: [Actions] Use vcpkg to provide libpng on macOSOwen Rudge
2021-02-14Add: [OSX] Native font rendering without using FreeType.Michael Lutz
2021-02-13Change: [Actions] Also run CI for VS2017glx22
2021-02-08Change: Convert .md to .rtf for Windows/Mac packagesOwen Rudge
2021-02-08Fix: [Actions] Use same vcpkg commit for CI on macOS as release buildsOwen Rudge
2021-02-05Codechange: [Actions] Document better why we build our own fluidsynth (#8646)Patric Stout
nielsmh nicely correct us in #8641, pointing out the old comment is not telling a complete truth. The result is the same, but it is better to not mislead future-us.
2021-02-05Add: [Actions] Automatically upload releases to Steam (#8644)Patric Stout
2021-02-05Feature: [Actions / CMake] support for generic linux builds (#8641)Patric Stout
These bundles can be opened on any "modern" Linux machine with a driver that SDL2 supports. Machines needs at least glibc 2.15, which was released 10 years ago. It is build with CentOS 7 as base, and only assumes the following libraries are available on the system: - libc - libdl - libgcc_s - libpthread - librt - libstdc++ All other libraries the game depends on are bundled together with the game, so users don't need any library installed to use this bundle. The downside of course is that this increases the binary size a bit: 30 MiB of libraries are in this bundle. RPATH is used to make ld-linux find the folder libraries are stored in; however, system libraries are always used before these, in the assumption libraries on the user system are more up-to-date. Using -DOPTION_PACKAGE_DEPENDENCIES=ON switches on packaging of libraries in the "lib" folder. This requires CMake 3.16 to be installed; otherwise it will fail.
2021-01-29Codechange: [Actions] we no longer need xdg-basedir (#8615)Patric Stout
This was already removed from the "ci-build", but not yet from "release".
2021-01-28Feature: [Actions] Create .zip for macOS buildOwen Rudge
2021-01-18Feature: [Actions] ARM64 builds for WindowsOwen Rudge
2021-01-18Fix: [Actions] Give Universal Mac packages the "universal" suffixOwen Rudge
2021-01-15Feature: Build macOS build as a universal binaryOwen Rudge
2021-01-14Fix: vcpkg binaries were not being cached on MacOwen Rudge
2021-01-14Fix: [Actions] circumvent Windows tar warning about read-only files (#8570)Patric Stout
This was already applied on the CI build, but not yet on the release build.
2021-01-14Fix: Remove .sha256 files from macOS buildsOwen Rudge
2021-01-13Feature: Sign macOS buildsOwen Rudge
2021-01-10Fix: add missing variables to NewGRF inspect window.frosch
2021-01-08Feature: Build ARM64 (Apple Silicon) version for macOSOwen Rudge
2021-01-08Fix: [Actions] circumvent Windows tar warning about read-only files (#8524)Patric Stout
Because certain files are read-only, the "restore-cache" step fails, as Windows tar refuses to overwrite those files (even if they are identical). Instead of hoping upstream fixes "restore-cache", just remove the read-only flag on these files instead.
2021-01-02Codechange: Drop libxdg-basedir dependency in favour of finding the ↵Charles Pigott
directories ourselves
2020-12-26Fix: [Actions] cmakeBuildType is only used with CMakeListsTxtBasic (#8435)Patric Stout
We use CMakeListsTxtAdvanced, and as such, we have to do this our self via "-DCMAKE_BUILD_TYPE=RelWithDebInfo". Otherwise we are producing Debug builds instead of Release builds. Oops.
2020-12-22Add: [GitHub] PR template. (#8414)frosch
2020-12-19Add: [Actions] release workflow for both releases and nightliesPatric Stout
This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-15Add: [Actions] preview workflow, where PRs can be reviewed in the browserPatric Stout
When a developer attaches the "preview" label, a build is created and published on https://preview.openttd.org/. After that, new pushes to the PR are automatically build (as long as the "preview" label exists). If a non-developer attaches the "preview" label, it will be removed.
2020-12-15Add: support for emscripten (play-OpenTTD-in-the-browser)Patric Stout
Emscripten compiles to WASM, which can be loaded via HTML / JavaScript. This allows you to play OpenTTD inside a browser. Co-authored-by: milek7 <me@milek7.pl>
2020-12-13Fix: [Actions] cleanup ci-build workflow to be up-to-date (#8375)Patric Stout
Also, while at it, make it more like the upcoming release-workflow, so they look a lot more similar. Functional it should be the same, except that Windows should now also output when a test fails.
2020-12-10Fix: Prevent infinite recursion in commit checkerglx22
2020-10-10Fix: [Actions] Call apt-get update before trying to install packagesCharles Pigott
2020-10-10Add: [Actions] Add problem matchers for CI platformsCharles Pigott
2020-10-03Add: [Actions] CI build workflowglx
2020-01-19Add: [Actions] commit-checker workflowglx
2019-08-31Add: [GitHub] sponsor button on github.com (#7700)Roger
2019-01-29Add: [GitHub] Add issue template to encourage better issue reporting. (#7137)PeterN
2019-01-24Add: [GitHub] enable probot/stale, to flush out stale issues/pull requestsPatric Stout
Stale bot checks if an issue hasn't had any attention in the last 60 days, or if a pull request hasn't had any attention in the last 30 days. If so, it marks it as stale. After 7 more days, it closes the issue/pull request. Any activity on the issue/pull request resets the timer. This helps keeping the counter low, and the work manageable. There is a lot of reasoning behind this idea, and other projects show it really helps to keep the issue/pull request count low. More information here: https://github.com/probot/stale