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-15 01:06:02 +01:00
|
|
|
# SPDX-FileCopyrightText: 2018 yuzu Emulator Project
|
|
|
|
|
# SPDX-License-Identifier: GPL-2.0-or-later
|
2016-03-01 17:24:18 +00:00
|
|
|
|
|
|
|
|
# This file provides the function windows_copy_files.
|
|
|
|
|
# This is only valid on Windows.
|
|
|
|
|
|
|
|
|
|
# Include guard
|
|
|
|
|
if(__windows_copy_files)
|
|
|
|
|
return()
|
|
|
|
|
endif()
|
|
|
|
|
set(__windows_copy_files YES)
|
|
|
|
|
|
|
|
|
|
# Any number of files to copy from SOURCE_DIR to DEST_DIR can be specified after DEST_DIR.
|
|
|
|
|
# This copying happens post-build.
|
|
|
|
|
function(windows_copy_files TARGET SOURCE_DIR DEST_DIR)
|
|
|
|
|
# windows commandline expects the / to be \ so switch them
|
|
|
|
|
string(REPLACE "/" "\\\\" SOURCE_DIR ${SOURCE_DIR})
|
|
|
|
|
string(REPLACE "/" "\\\\" DEST_DIR ${DEST_DIR})
|
|
|
|
|
|
|
|
|
|
# /NJH /NJS /NDL /NFL /NC /NS /NP - Silence any output
|
|
|
|
|
# cmake adds an extra check for command success which doesn't work too well with robocopy
|
|
|
|
|
# so trick it into thinking the command was successful with the || cmd /c "exit /b 0"
|
|
|
|
|
add_custom_command(TARGET ${TARGET} POST_BUILD
|
2018-06-24 20:27:00 +01:00
|
|
|
COMMAND ${CMAKE_COMMAND} -E make_directory ${DEST_DIR}
|
2016-03-01 17:24:18 +00:00
|
|
|
COMMAND robocopy ${SOURCE_DIR} ${DEST_DIR} ${ARGN} /NJH /NJS /NDL /NFL /NC /NS /NP || cmd /c "exit /b 0"
|
|
|
|
|
)
|
2018-06-24 20:27:00 +01:00
|
|
|
endfunction()
|
