build: use strategy matrix

[ReenigneArcher]

Description

Enable Unix builds.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c2ae74a) to head (bda3314).

Additional details and impacted files

@@             Coverage Diff              @@
##           master       #20       +/-   ##
============================================
+ Coverage   66.66%   100.00%   +33.33%     
============================================
  Files           2         2               
  Lines           3         4        +1     
  Branches        1         1               
============================================
+ Hits            2         4        +2     
+ Partials        1         0        -1     

Flag	Coverage Δ
Linux	50.00% <ø> (?)
Windows	66.66% <ø> (ø)
macOS	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes