Mirror of github.com/cira0100/Eglantine-public nx2, a fork of Djihads80/Eglantine. https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2 2022-07-27T10:53:49+00:00 2022-07-27T10:53:49+00:00 Andrea Pappacoda andrea@pappacoda.it 2022-05-15T00:06:02+00:00 urn:sha1:6a2efdda2f7075331cab36901a30d511468f60e7 [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 b2eb10382941bef0914f4a0a4685b9033440aa9f 2018-01-18T02:51:43+00:00 Lioncash mathew1800@gmail.com 2018-01-18T00:37:34+00:00 urn:sha1:447c25646ed2ea0cb0b553e4b53a9de267b821fb Removes the need to store to separate SRC and HEADER variables, and then construct the target in most cases. 2015-07-13T22:47:08+00:00 Yuri Kunde Schlesner yuriks@yuriks.net 2015-07-13T22:46:46+00:00 urn:sha1:516169945285aee0591111576a28a0dea86faab9 We already define _CRT_SECURE_NO_WARNINGS 2015-07-13T22:47:04+00:00 Yuri Kunde Schlesner yuriks@yuriks.net 2015-07-13T22:46:11+00:00 urn:sha1:1bf030f4af76f76d52b59f81572edd8e064a5284 INTERFACE doesn't define the symbol when compiling the library itself. PUBLIC should be used when the definition is needed both by the library and by the users. 2015-07-12T19:49:23+00:00 Greg Wicks gpwicks@email.wm.edu 2015-06-23T00:59:00+00:00 urn:sha1:9930ef72ddaf8930a9bf3e574b7de69f73ecbf87