Commit graph

15 commits

Author SHA1 Message Date
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
Kyle Kienapfel
5cda630417 package MSVC CI Builds differently, and include yuzu.exe
This is related to 8486

Ninja places the exe files into .\build\bin while MSBuild may place them
into .\build\bin\Release

upload.ps1 was originally written for use with Azure Dev Ops to cough up
about 5 files and the script appears to be used for both CI and
mainline builds

GHA (GitHub Actions) makes available a single zip of the items uploaded by
each Upload action (artifacts directory), so we want to work with that.

I'm doing changes to upload.ps1 to accomplish this.

The changes to the verify.yml are as follows

-DGIT_BRANCH=pr-verify changes the header in yuzu, instead of saying
HEAD-<hash>-dirty it'll say pr-verify-<hash>

-DCLANG_FORMAT_SUFFIX=discordplzdontclang tricks the CMake stuff for
discord-rpc to NOT run clang-format, as this was marking CI builds as
dirty

I'm also making it upload just the exe by itself, as the msvc builds are
quite chunky. but maybe this is unnecessary.

Currently the MSVC artifact option is a 274MB zip that contains 3 copies
of the DLLs, and 4 copies of the source tarball, and zero copies of yuzu.exe

This PR should have msvc artifacts of about 190MB that downloads as 81 MB zip
2022-07-23 08:35:26 -07:00
lat9nq
265d1d6979 ci,CMake: Integrate vcpkg into CMakeLists
Uses manifest mode if the bundled vcpkg is used.
2022-07-22 20:54:00 -04:00
Morph
4fa625c4fa ci: Update various actions from v2 to v3 2022-07-05 20:41:49 -04:00
liushuyu
9981ce8d98 CI: upload artifacts for pull request verification 2022-07-04 21:21:56 -06:00
liushuyu
40493231ed CI: fix caching 2022-07-04 21:21:56 -06:00
liushuyu
a1815b617c CI: Use GitHub Actions to check pull requests 2022-07-04 21:21:56 -06:00
FearlessTobi
07b82427ab .ci: Use Github Actions to update translation source files 2021-10-15 15:12:14 +02:00
tgsm
9ff3401133 .github: add a new issue template 2020-06-28 20:46:46 +02:00
Tobias
9738dc3058
.github: Create FUNDING.yml 2019-06-08 17:00:32 +02:00
Tobias
a6f473fd01
ISSUE_TEMPLATE: changes to make it more expressive and prevent low-quality issues 2019-01-22 21:52:59 +01:00
MerryMage
80db02c497 Minor cleanup 2018-01-13 23:56:18 +00:00
Alex Touchet
e46ec64690 Edit Citra URLs (#2728) 2017-06-03 23:51:45 +03:00
Kloen Lansfiel
9d0d77de1f github: fixed issue template forum links (#2470) 2017-01-24 10:23:03 -03:00
MerryMage
15f16e256c .github: Add ISSUE_TEMPLATE.md 2016-08-26 16:18:01 +01:00