summaryrefslogtreecommitdiffstats
path: root/externals/libusb/config.h.in (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-07-27chore: make yuzu REUSE compliantAndrea Pappacoda1-0/+5
[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
2020-08-26externals: Track upstream libusbLioncash1-0/+90
We can place the external in an inner folder and manage the custom files necessary to integrate it with CMake directly. This allows us to directly change how we use it with our build system, as opposed to needing to change a fork.
2020-08-26externals: Untrack non-upstream variant of libusbLioncash1-0/+0
We shouldn't be tracking personal forks of repositories when upstream can be managed directly.
2020-06-22update libusb dependencyAmeer1-0/+0
2020-06-22Update src/input_common/main.cppameerj1-0/+0
Co-authored-by: LC <mathew1800@gmail.com> update libusb submodule (hopefully windows build error fixed)
2020-06-21Add libusb dependencyAmeer1-0/+0