<feed xmlns='http://www.w3.org/2005/Atom'>
<title>yuzu-mainline/externals/getopt, branch master</title>
<subtitle>A backup of the Yuzu mainline repo. Only includes the master branch, nothing else.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/'/>
<entry>
<title>chore: make yuzu REUSE compliant</title>
<updated>2022-07-27T10:53:49+00:00</updated>
<author>
<name>Andrea Pappacoda</name>
<email>andrea@pappacoda.it</email>
</author>
<published>2022-05-15T00:06:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/commit/?id=cdb240f3d4d9c0d6d56e6660d8c45da4ab60ff59'/>
<id>cdb240f3d4d9c0d6d56e6660d8c45da4ab60ff59</id>
<content type='text'>
[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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
[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
</pre>
</div>
</content>
</entry>
<entry>
<title>CMakeLists: Derive the source directory grouping from targets themselves</title>
<updated>2018-01-18T02:51:43+00:00</updated>
<author>
<name>Lioncash</name>
<email>mathew1800@gmail.com</email>
</author>
<published>2018-01-18T00:37:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/commit/?id=e710a1b9894d835d740ed63c03098fd637f61f63'/>
<id>e710a1b9894d835d740ed63c03098fd637f61f63</id>
<content type='text'>
Removes the need to store to separate SRC and HEADER variables, and then
construct the target in most cases.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Removes the need to store to separate SRC and HEADER variables, and then
construct the target in most cases.
</pre>
</div>
</content>
</entry>
<entry>
<title>getopt: Fix macro redefinition warning</title>
<updated>2015-07-13T22:47:08+00:00</updated>
<author>
<name>Yuri Kunde Schlesner</name>
<email>yuriks@yuriks.net</email>
</author>
<published>2015-07-13T22:46:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/commit/?id=516169945285aee0591111576a28a0dea86faab9'/>
<id>516169945285aee0591111576a28a0dea86faab9</id>
<content type='text'>
We already define _CRT_SECURE_NO_WARNINGS
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We already define _CRT_SECURE_NO_WARNINGS
</pre>
</div>
</content>
</entry>
<entry>
<title>getopt: Fix compilation settings</title>
<updated>2015-07-13T22:47:04+00:00</updated>
<author>
<name>Yuri Kunde Schlesner</name>
<email>yuriks@yuriks.net</email>
</author>
<published>2015-07-13T22:46:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/commit/?id=1bf030f4af76f76d52b59f81572edd8e064a5284'/>
<id>1bf030f4af76f76d52b59f81572edd8e064a5284</id>
<content type='text'>
INTERFACE doesn't define the symbol when compiling the library itself.
PUBLIC should be used when the definition is needed both by the library
and by the users.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
INTERFACE doesn't define the symbol when compiling the library itself.
PUBLIC should be used when the definition is needed both by the library
and by the users.
</pre>
</div>
</content>
</entry>
<entry>
<title>Implement new argument parsing using getopt and add the corresponding library to externals</title>
<updated>2015-07-12T19:49:23+00:00</updated>
<author>
<name>Greg Wicks</name>
<email>gpwicks@email.wm.edu</email>
</author>
<published>2015-06-23T00:59:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benis.co.uk/yuzu-mainline/commit/?id=9930ef72ddaf8930a9bf3e574b7de69f73ecbf87'/>
<id>9930ef72ddaf8930a9bf3e574b7de69f73ecbf87</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
