Set up deployment - Githubissues

Description

TravisCI and AppVeyor both have been configured to push their build artifacts here on GitHub. On Linux only artifacts built by the latest stable compilers are uploaded. Artifacts are built in the release mode. Packages are supplied for both dynamic and static linking.

Packages name consist of: spmod-<os>-<spmod_ver>-<compiler>-<linktype>.<ext>

Where:

os - linux or win32
spmod_ver - spmod version
compiler - gcc or clang on Linux, empty for windows (should be msvc?)
linktype - dynamic or static
ext - tar.xz (Linux) or 7z (Windows)

Should we also include compiler version into compiler, like clang6, gcc8 and msvc2017?

Backwards incompatible changes

Meson option dynamic_link has been renamed to linktype and can be set to either dynamic or static.

Motivation and Context

Helps us make actual releases.

How has this been tested?

By pushing test releases.

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Amaroq7 / SPMod

Set up deployment #33