[sdl1-mixer] new port

[arbruijn]

Current github version, with custom msbuild files as with the sdl1 port and dependencies from vcpkg.

• Changes comply with the maintainer guide
• The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
• Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
• The versioning scheme in vcpkg.json matches what upstream says.
• The license declaration in vcpkg.json matches what upstream says.
• The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• The generated "usage text" is accurate. See adding-usage for context.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is in the new port's versions file.
• Only one version is added to each modified port's versions file.

[arbruijn]

@microsoft-github-policy-service agree

[BillyONeal]

It looks like this is a complete build system replacement. Is there a specific reason the replacement is done with msbuild rather than with something like cmake? I'm nervous about this replacement not being stable across updates.

[arbruijn]

I assumed the sdl1 port would be a good example. but if cmake is preferred I can look into that.

[BillyONeal]

I assumed the sdl1 port would be a good example. but if cmake is preferred I can look into that.

"copied from this other port" is a reasonable justification. This works, so I'm going to merge it as is, but would really appreciate CMake instead where possible.

Thanks!

[dg0yt]

IMO there are many old ports which are not good examples...
This msbuild stuff makes it hard for non-MSVC users to contribute.