[libsmacker] add new port

[dbarkar]

• 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 docs/examples/adding-an-explicit-usage.md 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.

[dbarkar]

@microsoft-github-policy-service agree

[dbarkar]

This is my first port, please let me know if I can make it better :)

[dg0yt]

Doesn't it build with its native build system and vcpkg_configure_make et al.?

[dbarkar]

It's just few files, I thought it would be better to write proper CMakeLists.txt and avoid autotools.
p.s> I tried vcpkg_configure_make and couldn't make it work with MSVC, is it supposed to work? If you believe that it's the best way, I can try and rework this port.

[dg0yt]

I tried vcpkg_configure_make and couldn't make it work with MSVC, is it supposed to work? If you believe that it's the best way, I can try and rework this port.

I cannot give the ultimate answer. I know about the pain with autotools on Windows, and some projects can't be made work at all. But having a vendored build system in vcpkg has downsides, too.