Skip to content

Commit c3debd3

Browse files
ctreffsctreffs
authoredMay 5, 2021
Setup for Github (#1)
* Setup for Github * Add code owners file * Update LICENSE * Remove dead link * Relax SDL version test * print SDL2 version * Test for minor version * Remove old CI * Update README
·
1.4.11.2.0
1 parent 8f41b01 commit c3debd3

17 files changed

+492
-71
lines changed
 

‎.github/FUNDING.yml

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
github: [ctreffs]
2+
custom: ['https://www.paypal.com/donate?hosted_button_id=GCG3K54SKRALQ']

‎.github/ISSUE_TEMPLATE/BUG_REPORT.md

+61
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
---
2+
name: 🐛 Bug Report
3+
about: Something isn't working as expected, create a report to help us improve
4+
labels: bug
5+
---
6+
7+
<!--
8+
Thanks for contributing to this project!
9+
10+
Before you submit your issue, please replace each paragraph
11+
below with the relevant details for your bug, and complete
12+
the steps in the checklist by placing an 'x' in each box:
13+
14+
- [x] I've completed this task
15+
- [ ] This task isn't completed
16+
-->
17+
18+
### Bug Description
19+
20+
*A clear and concise description of what the bug is.
21+
Replace this paragraph with a short description of the incorrect behavior.
22+
(If this is a regression, please note the last version of the package that exhibited the correct behavior in addition to your current version.)*
23+
24+
### Information
25+
26+
- **Package version:** What tag or branch of this package are you using? e.g. tag `1.2.3` or branch `main`
27+
- **Platform version:** Please tell us the version number of your operating system. e.g. `macOS 11.2.3` or `Ubuntu 20.04`
28+
- **Swift version:** Paste the output of `swift --version` here.
29+
30+
### Checklist
31+
32+
- [ ] If possible, I've reproduced the issue using the `main`/`master` branch of this package.
33+
- [ ] I've searched for existing issues under the issues tab.
34+
- [ ] The bug is reproducible
35+
36+
### Steps to Reproduce
37+
38+
*Steps to reproduce the behavior:*
39+
40+
1. Go to '...'
41+
2. '....'
42+
43+
*Replace this paragraph with an explanation of how to reproduce the incorrect behavior.
44+
Include a simple code example, if possible.*
45+
46+
### Expected behavior
47+
48+
*A clear and concise description of what you expected to happen.
49+
Describe what you expect to happen.*
50+
51+
### Actual behavior
52+
53+
*Describe or copy/paste the behavior you observe.*
54+
55+
### Screenshots
56+
57+
If applicable, add screenshots to help explain your problem.
58+
59+
### Additional context
60+
61+
*Add any other context about the problem here.*

‎.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

+31
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
name: 💡 Feature Request
3+
about: A suggestion for a new feature or idea for this project
4+
labels: enhancement
5+
---
6+
7+
<!--
8+
Thanks for contributing to this project!
9+
10+
Before you submit your issue, please replace the paragraphs
11+
below with information about your proposed feature.
12+
-->
13+
14+
### Feature request
15+
16+
*Replace this paragraph with a description of your proposed feature.
17+
A clear and concise description of what the idea or problem is you want to solve.
18+
Please be sure to describe some concrete use cases for the new feature -- be as specific as possible.
19+
Provide links to existing issues or external references/discussions, if appropriate.*
20+
21+
### Describe the solution you'd like
22+
23+
*A clear and concise description of what you want to happen.*
24+
25+
### Describe alternatives you've considered
26+
27+
*A clear and concise description of any alternative solutions or features you've considered.*
28+
29+
### Additional context
30+
31+
*Add any other context or screenshots about the feature request here.*

‎.github/ISSUE_TEMPLATE/config.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: false

‎.github/pull_request_template.md

+52
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
<!--
2+
Thanks for contributing to this project!
3+
4+
Before you submit your request, please replace each paragraph
5+
below with the relevant details, and complete the steps in the
6+
checklist by placing an 'x' in each box:
7+
8+
- [x] I've completed this task
9+
- [ ] This task isn't completed
10+
-->
11+
12+
### Description
13+
14+
*Replace this paragraph with a description of your changes and rationale.
15+
Provide links to an existing issue or external references/discussions, if appropriate.*
16+
17+
### Detailed Design
18+
19+
*Include any additional information about the design here. At minimum, describe a synopsis of any public API additions.*
20+
21+
```swift
22+
/// The new feature implemented by this pull request.
23+
public struct Example: Collection {
24+
}
25+
```
26+
27+
### Documentation
28+
29+
*How has the new feature been documented?
30+
Have the relevant portions of the guides in the Documentation folder been updated in addition to symbol-level documentation?*
31+
32+
### Testing
33+
34+
*How is the new feature tested?
35+
Please ensure CI is not broken*
36+
37+
### Performance
38+
39+
*How did you verify the new feature performs as expected?*
40+
41+
### Source Impact
42+
43+
*What is the impact of this change on existing users of this package? Does it deprecate or remove any existing API?*
44+
45+
### Checklist
46+
47+
- [ ] I've read the [Contribution Guidelines](https://github.com/ctreffs/SwiftSDL2/blob/master/CONTRIBUTING.md)
48+
- [ ] I've followed the coding style of the rest of the project.
49+
- [ ] I've added tests covering all new code paths my change adds to the project (to the extent possible).
50+
- [ ] I've added benchmarks covering new functionality (if appropriate).
51+
- [ ] I've verified that my change does not break any existing tests or introduce unexpected benchmark regressions.
52+
- [ ] I've updated the documentation (if appropriate).

‎.github/workflows/ci.yml

+80
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
name: CI
2+
3+
on:
4+
push:
5+
branches: [ master ]
6+
pull_request:
7+
branches: [ master ]
8+
9+
jobs:
10+
macOS:
11+
runs-on: macOS-latest
12+
strategy:
13+
matrix:
14+
xcode: ["12.4"]
15+
steps:
16+
- name: Checkout
17+
uses: actions/checkout@master
18+
- name: Restore cached Homebrew dependencies
19+
uses: actions/cache@v2
20+
with:
21+
path: |
22+
~/Library/Caches/Homebrew/sdl2--*
23+
~/Library/Caches/Homebrew/downloads/*--sdl2-*
24+
key: ${{ runner.os }}-brew-sdl2-${{ hashFiles('.github/brew-formulae') }}
25+
restore-keys: ${{ runner.os }}-brew-sdl2-
26+
- name: Restore cached SPM dependencies
27+
uses: actions/cache@v2
28+
with:
29+
path: |
30+
.build/repositories
31+
key: ${{ runner.os }}-spm-repos-${{ hashFiles('**/Package.resolved') }}
32+
restore-keys: |
33+
${{ runner.os }}-spm-repos-
34+
- name: Select Xcode ${{ matrix.xcode }}
35+
run: sudo xcode-select -s /Applications/Xcode_${{ matrix.xcode }}.app
36+
- name: Install dependencies
37+
run: |
38+
brew install sdl2
39+
sdl2-config --version
40+
- name: Test
41+
run: make test
42+
env:
43+
DEVELOPER_DIR: /Applications/Xcode_${{ matrix.xcode }}.app/Contents/Developer
44+
- name: Build Release
45+
run: make build-release
46+
env:
47+
DEVELOPER_DIR: /Applications/Xcode_${{ matrix.xcode }}.app/Contents/Developer
48+
49+
linux:
50+
runs-on: ubuntu-latest
51+
strategy:
52+
matrix:
53+
swift: ["latest"]
54+
container:
55+
image: swift:${{ matrix.swift }}
56+
steps:
57+
- name: Checkout
58+
uses: actions/checkout@master
59+
- name: Restore APT cache
60+
uses: actions/cache@v2
61+
with:
62+
path: /var/cache/apt
63+
key: ${{ runner.os }}-apt
64+
- name: Restore cached SPM dependencies
65+
uses: actions/cache@v2
66+
with:
67+
path: |
68+
.build/repositories
69+
key: ${{ runner.os }}-spm-repos-${{ hashFiles('**/Package.resolved') }}
70+
restore-keys: |
71+
${{ runner.os }}-spm-repos-
72+
- name: Install dependencies
73+
run: |
74+
apt update
75+
apt-get install -y libsdl2-dev
76+
sdl2-config --version
77+
- name: Test
78+
run: make test
79+
- name: Build Release
80+
run: make build-release

‎.github/workflows/markdown-link-check.yml

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
name: Check markdown links
2+
3+
on: push
4+
5+
jobs:
6+
markdown-link-check:
7+
runs-on: ubuntu-latest
8+
steps:
9+
- name: Checkout
10+
uses: actions/checkout@master
11+
- name: markdown-link-check
12+
uses: gaurav-nelson/github-action-markdown-link-check@master
13+

‎.gitlab-ci.yml

-34
This file was deleted.

‎.swift-version

-1
This file was deleted.

‎.travis.yml

-25
This file was deleted.

‎CODEOWNERS

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# This file is a list of the people responsible for ensuring that contributions
2+
# to this projected are reviewed, either by themselves or by someone else.
3+
# They are also the gatekeepers for their part of this project, with the final
4+
# word on what goes in or not.
5+
# The code owners file uses a .gitignore-like syntax to specify which parts of
6+
# the codebase is associated with an owner. See
7+
# <https://docs.github.com/github/creating-cloning-and-archiving-repositories/about-code-owners>
8+
# for details.
9+
# The following lines are used by GitHub to automatically recommend reviewers.
10+
# Each line is a file pattern followed by one or more owners.
11+
12+
* @ctreffs

‎CODE_OF_CONDUCT.md

+136
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement
63+
e.g. via [content abuse report][ref-report-abuse].
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][ref-homepage-cc],
118+
version 2.0, available at
119+
<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
For answers to common questions about this code of conduct, see the FAQ at
125+
<https://www.contributor-covenant.org/faq>.
126+
Translations are available at
127+
<https://www.contributor-covenant.org/translations>.
128+
129+
<!-- REFERENCES -->
130+
131+
[ref-homepage-cc]: https://www.contributor-covenant.org
132+
[ref-report-abuse]: https://docs.github.com/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam#reporting-an-issue-or-pull-request
133+
[ref-gh-coc]: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project
134+
[ref-gh-abuse]: https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository
135+
[ref-coc-guide]: https://opensource.guide/code-of-conduct/
136+

‎CONTRIBUTING.md

+95
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
# 💁 Contributing to this project
2+
3+
4+
> First off, thank you for considering contributing to this project.
5+
> It’s [people like you][ref-contributors] that keep this project alive and make it great!
6+
> Thank you! 🙏💜🎉👍
7+
8+
The following is a set of **guidelines for contributing** to this project.
9+
Use your best judgment and feel free to propose changes to this document in a pull request.
10+
11+
**Working on your first Pull Request?** You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github)
12+
13+
### 💡 Your contribution - the sky is the limit 🌈
14+
15+
This is an open source project and we love to receive contributions from our community — [**you**][ref-contributors]!
16+
17+
There are many ways to contribute, from writing __tutorials__ or __blog posts__, improving the [__documentation__][ref-documentation], submitting [__bug reports__][ref-issues-new] and [__enhancement__][ref-pull-request-new] or
18+
[__writing code__][ref-pull-request-new] which can be incorporated into the repository itself.
19+
20+
When contributing to this project, please feel free to discuss the changes and ideas you wish to contribute with the repository owners before making a change by opening a [new issue][ref-issues-new] and add the **feature request** tag to that issue.
21+
22+
Note that we have a [code of conduct][ref-code-of-conduct], please follow it in all your interactions with the project.
23+
24+
### 🐞 You want to report a bug or file an issue?
25+
26+
1. Ensure that it was **not already reported** and is being worked on by checking [open issues][ref-issues].
27+
2. Create a [new issue][ref-issues-new] with a **clear and descriptive title**
28+
3. Write a **detailed comment** with as much relevant information as possible including
29+
- *how to reproduce* the bug
30+
- a *code sample* or an *executable test case* demonstrating the expected behavior that is not occurring
31+
- any *files that could help* trace it down (i.e. logs)
32+
33+
### 🩹 You wrote a patch that fixes an issue?
34+
35+
1. Open a [new pull request (PR)][ref-pull-request-new] with the patch.
36+
2. Ensure the PR description clearly describes the problem and solution.
37+
3. Link the relevant **issue** if applicable ([how to link issues in PRs][ref-pull-request-how-to]).
38+
4. Ensure that [**no tests are failing**][ref-gh-actions] and **coding conventions** are met
39+
5. Submit the patch and await review.
40+
41+
### 🎁 You want to suggest or contribute a new feature?
42+
43+
That's great, thank you! You rock 🤘
44+
45+
If you want to dive deep and help out with development on this project, then first get the project [installed locally][ref-readme].
46+
After that is done we suggest you have a look at tickets in our [issue tracker][ref-issues].
47+
You can start by looking through the beginner or help-wanted issues:
48+
- [__Good first issues__][ref-issues-first] are issues which should only require a few lines of code, and a test or two.
49+
- [__Help wanted issues__][ref-issues-help] are issues which should be a bit more involved than beginner issues.
50+
These are meant to be a great way to get a smooth start and won't put you in front of the most complex parts of the system.
51+
52+
If you are up to more challenging tasks with a bigger scope, then there are a set of tickets with a __feature__, __enhancement__ or __improvement__ tag.
53+
These tickets have a general overview and description of the work required to finish.
54+
If you want to start somewhere, this would be a good place to start.
55+
That said, these aren't necessarily the easiest tickets.
56+
57+
For any new contributions please consider these guidelines:
58+
59+
1. Open a [new pull request (PR)][ref-pull-request-new] with a **clear and descriptive title**
60+
2. Write a **detailed comment** with as much relevant information as possible including:
61+
- What your feature is intended to do?
62+
- How it can be used?
63+
- What alternatives where considered, if any?
64+
- Has this feature impact on performance or stability of the project?
65+
66+
#### Your contribution responsibilities
67+
68+
Don't be intimidated by these responsibilities, they are easy to meet if you take your time to develop your feature 😌
69+
70+
- [x] Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
71+
- [x] Ensure (cross-)platform compatibility for every change that's accepted. An addition should not reduce the number of platforms that the project supports.
72+
- [x] Ensure **coding conventions** are met. Lint your code with the project's default tools. Project wide commands are available through the [Makefile][ref-makefile] in the repository root.
73+
- [x] Add tests for your feature that prove it's working as expected. Code coverage should not drop below its previous value.
74+
- [x] Ensure none of the existing tests are failing after adding your changes.
75+
- [x] Document your public API code and ensure to add code comments where necessary.
76+
77+
78+
### ⚙️ How to set up the environment
79+
80+
Please consult the [README][ref-readme] for installation instructions.
81+
82+
<!-- REFERENCES -->
83+
84+
[ref-code-of-conduct]: https://github.com/ctreffs/SwiftSDL2/blob/master/CODE_OF_CONDUCT.md
85+
[ref-contributors]: https://github.com/ctreffs/SwiftSDL2/graphs/contributors
86+
[ref-documentation]: https://github.com/ctreffs/SwiftSDL2/wiki
87+
[ref-gh-actions]: https://github.com/ctreffs/SwiftSDL2/actions
88+
[ref-issues-first]: https://github.com/ctreffs/SwiftSDL2/issues?q=is%3Aopen+is%3Aissue+label%3A"good+first+issue"
89+
[ref-issues-help]: https://github.com/ctreffs/SwiftSDL2/issues?q=is%3Aopen+is%3Aissue+label%3A"help+wanted"
90+
[ref-issues-new]: https://github.com/ctreffs/SwiftSDL2/issues/new/choose
91+
[ref-issues]: https://github.com/ctreffs/SwiftSDL2/issues
92+
[ref-pull-request-how-to]: https://docs.github.com/github/writing-on-github/autolinked-references-and-urls
93+
[ref-pull-request-new]: https://github.com/ctreffs/SwiftSDL2/compare
94+
[ref-readme]: https://github.com/ctreffs/SwiftSDL2/blob/master/README.md
95+
[ref-makefile]: https://github.com/ctreffs/SwiftSDL2/blob/master/Makefile

‎LICENSE

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
Copyright (c) 2019-2020 Christian Treffs
1+
Copyright (c) 2019-2021 Christian Treffs
22

33
This software is provided 'as-is', without any express or implied
44
warranty. In no event will the authors be held liable for any damages

‎Makefile

+6-1
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,14 @@ genLinuxTests:
99
swift test --generate-linuxmain
1010
swiftlint autocorrect --format --path Tests/
1111

12-
test: genLinuxTests
12+
.PHONY: test
13+
test:
1314
swift test
1415

16+
.PHONY: build-release
17+
build-release:
18+
swift build -c release
19+
1520
submodule:
1621
git submodule update --init --recursive
1722

‎README.md

+1-5
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
# <img src="https://www.libsdl.org/media/SDL_logo.png" height="20" max-width="90%" alt="SDL2" /> Swift SDL2
33

4-
[![Build Status](https://travis-ci.com/ctreffs/SwiftSDL2.svg?branch=master)](https://travis-ci.com/ctreffs/SwiftSDL2)
4+
[![CI](https://github.com/ctreffs/SwiftSDL2/actions/workflows/ci.yml/badge.svg)](https://github.com/ctreffs/SwiftSDL2/actions/workflows/ci.yml)
55
[![license](https://img.shields.io/badge/license-zlib-brightgreen.svg)](LICENSE)
66
[![swift version](https://img.shields.io/badge/swift-5.1+-brightgreen.svg)](https://swift.org/download)
77
[![platforms](https://img.shields.io/badge/platforms-%20macOS%20|%20iOS%20|%20tvOS-brightgreen.svg)](#)
@@ -23,7 +23,6 @@ These instructions will get your copy of the project up and running on your loca
2323

2424
* [Swift Package Manager (SPM)](https://github.com/apple/swift-package-manager)
2525
* [Swiftlint](https://github.com/realm/SwiftLint) for linting - (optional)
26-
* [SwiftEnv](https://swiftenv.fuller.li/) for Swift version management - (optional)
2726

2827
### 💻 Installing
2928

@@ -156,8 +155,6 @@ If you are interested in contributing, please feel free to do so!
156155
Things that need to be done are, among others:
157156

158157
- [ ] Wrap more SDL2 functions and types
159-
- [ ] Support for [Cocoapods](https://cocoapods.org) packaging
160-
- [ ] Support for [Carthage](https://github.com/Carthage/Carthage) packaging
161158
- [ ] Write some additional tests to improve coverage
162159

163160
## 🏷️ Versioning
@@ -190,7 +187,6 @@ See <https://www.libsdl.org/credits.php>
190187
* <https://github.com/latencyzero/CSDL2>
191188
* <https://github.com/lightive/CSDL2>
192189
* <https://github.com/sunlubo/CSDL2>
193-
* <https://github.com/MattGuerrette/CSDL2>
194190
* <https://github.com/KevinVitale/SwiftSDL>
195191
* <https://github.com/adagio/swiftsdl2>
196192
* <https://github.com/latencyzero/SwiftSDL>

‎Tests/CSDL2Tests/CSDL2Tests.swift

+1-4
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,8 @@ final class CSDL2Tests: XCTestCase {
2121

2222
XCTAssertEqual(compiled.major, 2)
2323
XCTAssertEqual(compiled.minor, 0)
24-
XCTAssertGreaterThanOrEqual(compiled.patch, 10)
25-
24+
2625
XCTAssertEqual(linked.major, 2)
2726
XCTAssertEqual(linked.minor, 0)
28-
XCTAssertGreaterThanOrEqual(compiled.patch, 10)
29-
3027
}
3128
}

0 commit comments

Comments
 (0)
Please sign in to comment.