Right now the first mention of Wine is down next to the download link, and no mention is made of it under the system requirements. Given that compatibility with Wine has been a goal for this project in the past (in terms of bugfixes that fixed issues that only emerged when using it), I thought it would be a good idea to show that this use case is indeed considered by the developers. As a Linux user myself, this kind of thing would be more likely to consider using Cxbx after glancing at the repository.
Make into one yml, rename to CI;
if conditions and search filtering make multiple ymls unneeded.
Build all branches.
Ignore unrelated files.
Build with VS2019 and VS2017.
Set fail-fast to false.
Add Debug configuration, and reorder configurations to be consistent.
Don't use master version of actions.
Fetch submodules with new addition to checkout action.
Build in the build directory.
Use -j to potentially speed up building.
Use default shell/robocopy for artifact preparation.
Add SDL2 to artifacts.
Add artifacts for PRs.
Only do artifacts for Release.
Change artifact path to artifacts. (the trailing slash isn't needed)
Change artifact name.
Add release creation job:
This creates a release with VS2019 and VS2017 builds using a CI-shortcommithash tag;
For example, CI-31d4ea3
This job is only ran for commits (push) to master, not pull requests, other branches, or forks.
Add badge to README
README improvements
Deleted trailing whitespace.
Raised minimum GPU requirements, and removed LLE GPU since it's disabled.
Make links more direct, and update outdated links.
Removed redundant Development Builds header.
Link to readme instead of directly to compatibility issues so people read the readme.
Move Compiling note where it makes more sense.
Seperated/formatted building steps and made them less confusing.
Grammar/spelling fixes.
Randomly generate Mac and Serial for new EEPROMs: Thanks dracc
Delay load pcap: Allows the emulator to run (without networking) when pcap isn't present
Having multiple build types for each branch is proving to be confusing for some users.
Ever since we implemented #1388, there has been no end-user benefit for using Debug builds, as they can get the same logging result by toggling the log level to Debug
RadWolfie