[slamd] Add new port

[Robertleoj]

If this PR adds a new port, please uncomment and fill out this checklist:

• [ x] 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.
• [x ] 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.
• [ x] The versioning scheme in vcpkg.json matches what upstream says.
• [ ]x The license declaration in vcpkg.json matches what upstream says.
• [ ]x The installed as the "copyright" file matches what upstream says.
• The source code of the component installed comes from an authoritative source.
• [ x] The generated "usage text" is accurate. See adding-usage for context.
• [ x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• [ ]x Only one version is in the new port's versions file.
• [ x] Only one version is added to each modified port's versions file.

[Robertleoj]

@microsoft-github-policy-service agree

[Robertleoj]

The build is failing for exactly the triplet that I am using (x64_linux), but it builds fine for me. I can't seem to access the build log - what could be going wrong here?

[LilyWangLL]

You could check and download the failure logs from: https://dev.azure.com/vcpkg/public/_build/results?buildId=114510&view=artifacts&pathAsName=false&type=publishedArtifacts.

[Robertleoj]

@LilyWangLL the build fails on

#include <format>

which is a c++20 feature - do you not support it? I specify that the project follows c++23 standard with

set(CMAKE_CXX_STANDARD 23)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

Any reason that this doesn't work?