[yoctolib] new port

[nickdademo]

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

[dg0yt]

Please use LF line endings.

[nickdademo]

Note: Removed Android support in this port as vendor has a different lib for that: https://github.com/yoctopuce/yoctolib_android

[nickdademo]

@dg0yt Are you able to take another look? (before I try and de-vendor mbedtls)

[dg0yt]

A few more nitpicks. But LGTM.

[BillyONeal]

Thanks for the new port!

@dg0yt Thanks for the review!

[srinsoz]

Hi, we’ve just discovered the existence of this vcpkg package and noticed that it is already outdated. How can we contribute to keeping this package up to date?

[nickdademo]

Hi, we’ve just discovered the existence of this vcpkg package and noticed that it is already outdated. How can we contribute to keeping this package up to date?

@srinsoz Ah, looks like you've published releases since I created this port - nice :)

Updating the port should just be a matter of bumping the relevant version and hash. However, you'll notice that 3 patches are applied to your source - definitely would be nice if these changes were made upstream on your end ;) (especially the exporting of a CMake config).

[srinsoz]

So, if I understand correctly, to keep this package up to date with our releases, we need to create a pull request in this repository with the updated vcpkg.json and vcpkg-configuration.json files each time we publish a new release. Is that correct?
Additionally, since we plan to officially add our library to vcpkg, should we remove the "Unofficial::" prefix?

[nickdademo]

So, if I understand correctly, to keep this package up to date with our releases, we need to create a pull request in this repository with the updated vcpkg.json and vcpkg-configuration.json files each time we publish a new release. Is that correct? Additionally, since we plan to officially add our library to vcpkg, should we remove the "Unofficial::" prefix?

Update vcpkg.json and portfile.cmake. If your upstream repo provides the CMake config, then the unofficial:: prefix can be removed (as that patch would no longer be needed).