[bark] New port v0.3.0
bark is a modern, low latency datadog client for C++.
- [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_packagecalls are REQUIRED, are satisfied byvcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx. - [x] The versioning scheme in
vcpkg.jsonmatches what upstream says. - [x] The license declaration in
vcpkg.jsonmatches what upstream says. - [x] The installed as the "copyright" file matches what upstream says.
- [x] 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 --alland 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.
I opted to override windows shared library builds to be static, since the library does not yet produce the correct DLLs.
There was a networking mistake last night affecting all osx builds but there are unrelated failures here so I'm skipping rerunning that.
There was a networking mistake last night affecting all osx builds but there are unrelated failures here so I'm skipping rerunning that.
It now compiles in CI on supported platforms.
Is it possible to get this merged?
The usage has been tested successfully locally on x64-windows.