[cglm] New port

[chausner]

Describe the pull request

• What does your PR fix?

  Adds new port for cglm

• Which triplets are supported/not supported? Have you updated the CI baseline?

  Note sure yet, Yes

• Does your PR follow the maintainer guide?

  Yes

• If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

  Yes

[chausner]

Adheres to semver according to https://github.com/recp/cglm/blob/master/docs/source/version.rst.

[BillyONeal]

• 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.

Can you please confirm that the following looks correct? (The upstream instructions use add_subdirectory :(

cglm provides CMake targets:

    find_package(cglm CONFIG REQUIRED)
    target_link_libraries(main PRIVATE cglm::cglm)

• 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.

[chausner]

Can you please confirm that the following looks correct? (The upstream instructions use add_subdirectory :(

Yes that should be correct but I have not tested it. They do write in their README (albeit without an example):

or you can use find_package to configure cglm

In their tests, they link with

target_link_libraries(${TEST_MAIN} PRIVATE cglm)

but I assume this is equivalent to linking with cglm::cglm.

[BillyONeal]

Added usage. Will merge as soon as build comes back. Thank you!