Commit Graph

14 Commits

Author SHA1 Message Date
Morph
118503f6e5 ci: Enable building with Visual Studio 2022 (again)
Since the following https://developercommunity.visualstudio.com/t/Type-alias-lookup-failure-within-paramet/10039150 compiler bug has been fixed, we can finally build with VS 2022 again.
2022-08-30 14:33:26 -04:00
bunnei
52dd68cfff
Merge pull request from yuzu-emu/revert-8256-ci-vs-2022
Revert "ci: Enable building with Visual Studio 2022"
2022-07-28 12:50:07 -07:00
Andrea Pappacoda
cdb240f3d4
chore: make yuzu REUSE compliant
[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 01cf05bc75
2022-07-27 12:53:49 +02:00
bunnei
3f37e228a3 Revert "ci: Enable building with Visual Studio 2022" 2022-07-22 17:59:12 -07:00
Morph
1193f7c393 ci: Update vmImage to windows-2022
The windows-2022 image contains Visual Studio 2022.
2022-04-24 23:36:59 -04:00
ameerj
1ea303e2af ci: Use ubuntu-latest vmImage where applicable
Not specifying the vmImage defaults to ubuntu-16.04, which will be deprecated soon and is experiencing brownouts.
2021-10-11 16:57:41 -04:00
bunnei
c104e9c698
ci: Increase mainline build timeout.
- We're currently timing out with builds exceeding 60M. This doubles the timeout to 120M.
2021-07-21 13:03:20 -07:00
Zach Hilman
59e75f4372 ci: Update to Windows Server 2019 and Visual Studio 2019
This updates to the latest available toolchain for MSVC builds.
2020-04-04 16:13:57 -04:00
Zach Hilman
1817191d55 ci: Isolate upload merge step into stage 2 2019-10-08 19:52:02 -04:00
Zach Hilman
d45ad75404 ci: Add version counter variable 2019-10-05 00:09:11 -04:00
Zach Hilman
a86e52a375 ci: Correct mainline release dependency 2019-10-02 18:54:05 -04:00
Zach Hilman
d648cd562a ci: Use MSVC windows for patreon 2019-10-02 18:23:09 -04:00
Zach Hilman
bfa60e2d4e ci: Use MSVC windows for mainline 2019-10-02 17:58:52 -04:00
Zach Hilman
cc3db2aa43 ci: Split mainline pipeline and add support for GitHub releases ()
* ci: Add mock build alternative for fast testing

* ci: Always cache build

* ci: Extract steps to download build stage artifacts

* ci: Add template to release to GitHub

* ci: Add template to release to Azure Universal Artifacts

* ci: Split mainline to two pipelines
2019-09-22 20:01:29 +00:00