Skip to content
Snippets Groups Projects
  1. Mar 18, 2023
  2. Sep 21, 2022
  3. Sep 05, 2022
  4. Jul 27, 2022
    • Andrea Pappacoda's avatar
      chore: make yuzu REUSE compliant · cdb240f3
      Andrea Pappacoda authored
      [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 01cf05bc
      cdb240f3
  5. Jul 24, 2022
  6. Apr 16, 2022
  7. Mar 20, 2022
  8. Feb 02, 2022
  9. Nov 25, 2021
  10. Oct 07, 2021
  11. Jan 24, 2021
  12. Jan 01, 2021
  13. Nov 16, 2020
  14. Sep 05, 2020
  15. Sep 04, 2020
  16. Aug 29, 2020
  17. Aug 27, 2020
    • Lioncash's avatar
      input_common: Eliminate most global state · 9e1b0af2
      Lioncash authored
      Abstracts most of the input mechanisms under an InputSubsystem class
      that is managed by the frontends, eliminating any static constructors
      and destructors. This gets rid of global accessor functions and also
      allows the frontends to have a more fine-grained control over the
      lifecycle of the input subsystem.
      
      This also makes it explicit which interfaces rely on the input subsystem
      instead of making it opaque in the interface functions. All that remains
      to migrate over is the factories, which can be done in a separate
      change.
      9e1b0af2
  18. Aug 26, 2020
  19. Sep 17, 2019
  20. Aug 02, 2019
  21. Jun 06, 2019
    • Lioncash's avatar
      yuzu/configuration: Make all widgets and dialogs aware of language changes · c09ff382
      Lioncash authored
      To prepare for translation support, this makes all of the widgets
      cognizant of the language change event that occurs whenever
      installTranslator() is called and automatically retranslates their text
      where necessary.
      
      This is important as calling the backing UI's retranslateUi() is often
      not enough, particularly in cases where we add our own strings that
      aren't controlled by it. In that case we need to manually refresh the
      strings ourselves.
      c09ff382
  22. Jun 05, 2019
  23. May 19, 2019
  24. Dec 05, 2018
  25. Dec 02, 2018
    • Lioncash's avatar
      yuzu/configuration/configure_input: Default destructor in the cpp file · f3253d0f
      Lioncash authored
      The previous code could potentially be a compilation issue waiting to
      occur, given we forward declare the type for a std::unique_ptr. If the
      complete definition of the forward declared type isn't visible in a
      translation unit that the class is used in, then it would fail to
      compile.
      
      Defaulting the destructor in a cpp file ensures the std::unique_ptr's
      destructor is only invoked where its complete type is known.
      f3253d0f
Loading