summaryrefslogtreecommitdiffstats
path: root/externals/libusb/CMakeLists.txt (unfollow)
Commit message (Collapse)AuthorFilesLines
2023-10-22externals/libusb: remove the GUID override workaround ...liushuyu1-7/+0
... on Windows MSVC, it seems to have been fixed
2023-05-24cmake: apply defaults to all externalsAlexandre Bouvier1-1/+1
2022-12-06cmake: prefer system libusbAlexandre Bouvier1-0/+2
2022-09-20cmake: Fix FindPkgConfigAlexandre Bouvier1-1/+1
2022-07-27chore: make yuzu REUSE compliantAndrea Pappacoda1-0/+3
[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
2021-07-06cmake: Specify the compiler on autotools externalslat9nq1-0/+2
Enables CCache on externals if available.
2021-06-26libusb: Apple is a POSIX systemMerryMage1-1/+1
2021-06-13cmake: Fix find_program usage for 3.15lat9nq1-0/+11
yuzu requires CMake 3.15 yet find_program was using REQUIRED, which is only available on 3.18 and later. Instead, we check for "<VAR>-NOTFOUND". In addition, check for additional requirements before building libusb or FFmpeg with autotools. Otherwise, CMake configuration will pass yet compilation will fail.
2021-06-11externals: Don't set FOUND or VERSION on LIBUSBlat9nq1-3/+3
Fixes an issue where libusb.h wouldn't be found when building yuzu on MSVC. This only affects the "traditional" CMake pathway for linking libusb to yuzu AKA MSVC. For autotools we still want to set these variables before configuring SDL.
2021-06-03externals: libusb: Call program names not full pathslat9nq1-4/+4
2021-06-03externals: libusb: Link libusb statically on Linuxlat9nq1-11/+13
Turns out that this is possible. Also addresses my own review comment.
2021-06-03cmake: General improvements to libusb linkinglat9nq1-9/+15
Delegates libusb external communication to externals/CMakeLists.txt Ensures an interface library `usb` for every pathway input_common just links to the `usb` library now externals/libusb/CMakeLists.txt sets variables to override SDL2's libusb finding Other minor cleanup
2021-06-03cmake: Use autotools to build libusb generally for GNUlat9nq1-16/+28
Building libusb was also broken on GCC (and maybe Clang) on our CMakeLists after upgrading to 1.0.24, but it was not being checked because our 18.04 container had libusb installed on it. This builds on the MinGW work from earlier and extends it to the rest of the GNU toolchains. In addition we make use of pkg-config when present to find libusb. pkg-config is preferrable because we can specify a minimum required version.
2021-05-31externals: libusb: Use autotools for MinGWlat9nq1-138/+222
After updating to 1.0.24, MinGW fails to build libusb as a result of numerous errors. So we build libusb their way and let them update the nontrivial stuff. This only applies to MinGW: the old path is still in use for Linux toolchains as well as MSVC. This will dynamically link libusb, since I hit build errors with the old way we used to resolve the conflict with SDL2.
2021-05-21Update libusb to 1.0.24german771-3/+3
2021-03-15externals/libusb/CMakeLists: Add /utf-8 compile option for MSVCMorph1-0/+5
2020-09-03externals: Work around libusb duplicate GUID errorsLioncash1-0/+3
Given we have two libraries that seem to use the same identifier, we can alter one of them so that the variable is used in place, effectively changing the used identifier, but without altering the source of libusb.
2020-08-26externals: Track upstream libusbLioncash1-0/+147
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