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 01cf05bc75b1e47beb08937439f3ed9339e7b254
2022-05-14 20:06:02 -04:00
|
|
|
// SPDX-FileCopyrightText: 2014 Citra Emulator Project
|
|
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
2014-11-02 14:34:14 -05:00
|
|
|
|
|
|
|
#pragma once
|
|
|
|
|
2015-01-20 20:16:47 -05:00
|
|
|
#include <utility>
|
2016-09-17 20:38:01 -04:00
|
|
|
#include "common/common_funcs.h"
|
2015-01-11 10:32:31 -05:00
|
|
|
|
2014-11-02 14:34:14 -05:00
|
|
|
namespace detail {
|
2016-09-17 20:38:01 -04:00
|
|
|
template <typename Func>
|
|
|
|
struct ScopeExitHelper {
|
2020-12-05 11:40:14 -05:00
|
|
|
explicit ScopeExitHelper(Func&& func_) : func(std::move(func_)) {}
|
2016-09-17 20:38:01 -04:00
|
|
|
~ScopeExitHelper() {
|
2020-03-31 15:16:07 -04:00
|
|
|
if (active) {
|
|
|
|
func();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void Cancel() {
|
|
|
|
active = false;
|
2016-09-17 20:38:01 -04:00
|
|
|
}
|
2014-11-02 14:34:14 -05:00
|
|
|
|
2016-09-17 20:38:01 -04:00
|
|
|
Func func;
|
2020-03-31 15:16:07 -04:00
|
|
|
bool active{true};
|
2016-09-17 20:38:01 -04:00
|
|
|
};
|
2014-11-02 14:34:14 -05:00
|
|
|
|
2016-09-17 20:38:01 -04:00
|
|
|
template <typename Func>
|
|
|
|
ScopeExitHelper<Func> ScopeExit(Func&& func) {
|
2019-04-11 20:01:31 -04:00
|
|
|
return ScopeExitHelper<Func>(std::forward<Func>(func));
|
2016-09-17 20:38:01 -04:00
|
|
|
}
|
2018-01-20 02:48:02 -05:00
|
|
|
} // namespace detail
|
2014-11-02 14:34:14 -05:00
|
|
|
|
|
|
|
/**
|
|
|
|
* This macro allows you to conveniently specify a block of code that will run on scope exit. Handy
|
|
|
|
* for doing ad-hoc clean-up tasks in a function with multiple returns.
|
|
|
|
*
|
|
|
|
* Example usage:
|
|
|
|
* \code
|
|
|
|
* const int saved_val = g_foo;
|
|
|
|
* g_foo = 55;
|
|
|
|
* SCOPE_EXIT({ g_foo = saved_val; });
|
|
|
|
*
|
|
|
|
* if (Bar()) {
|
|
|
|
* return 0;
|
|
|
|
* } else {
|
|
|
|
* return 20;
|
|
|
|
* }
|
|
|
|
* \endcode
|
|
|
|
*/
|
2015-01-11 10:32:31 -05:00
|
|
|
#define SCOPE_EXIT(body) auto CONCAT2(scope_exit_helper_, __LINE__) = detail::ScopeExit([&]() body)
|
2021-01-31 19:54:10 -05:00
|
|
|
|
|
|
|
/**
|
|
|
|
* This macro is similar to SCOPE_EXIT, except the object is caller managed. This is intended to be
|
|
|
|
* used when the caller might want to cancel the ScopeExit.
|
|
|
|
*/
|
|
|
|
#define SCOPE_GUARD(body) detail::ScopeExit([&]() body)
|