- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [x] SHA512s are updated for each updated download.
- [ ] The "supports" clause reflects platforms that may be fixed by this
new version.
- [ ] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [ ] Any patches that are no longer applied are deleted from the port's
directory.
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [x] SHA512s are updated for each updated download.
- [x] The "supports" clause reflects platforms that may be fixed by this
new version.
- [ ] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [ ] Any patches that are no longer applied are deleted from the port's
directory.
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
opentelemetry-cpp[geneva] depends on opentelemetry-cpp[etw] on Windows,
as the Geneva exporter applies header files on top of ETW exporter
header files. Without declaration this dependency in vcpkg, the user
would need to install both features manually to make it work, like
opentelemetry[etw,geneva].
- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [x] SHA512s are updated for each updated download.
- [x] The "supports" clause reflects platforms that may be fixed by this
new version.
- [ ] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [ ] Any patches that are no longer applied are deleted from the port's
directory.
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
<!-- If your PR fixes issues, please note that here by adding "Fixes
#NNNNNN." for each fixed issue on separate lines. -->
<!-- If you are still working on the PR, open it as a Draft:
https://github.blog/2019-02-14-introducing-draft-pull-requests/. -->
<!-- If this PR updates an existing port, please uncomment and fill out
this checklist:
- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [x] SHA512s are updated for each updated download.
- [x] The "supports" clause reflects platforms that may be fixed by this
new version.
- [x] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [x] Any patches that are no longer applied are deleted from the port's
directory.
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
END OF PORT UPDATE CHECKLIST (delete this line) -->
Upgrade to v1.14.0 release of OpenTelemetry-Cpp
https://github.com/open-telemetry/opentelemetry-cpp/releases/tag/v1.14.0.
The opentelemetry-cpp[geneva] feature was also updated to reflect the
change in v1.14.0
The port opentelemetry-fluentd depends on opentelemetry-cpp, and it is
broken on this upgrade, so it is deleted because it has been moved to
opentelemetry-cpp[geneva] in this PR.
<!-- If this PR adds a new port, please uncomment and fill out this
checklist:
- [ ] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] 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](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html).
- [ ] 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](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/examples/adding-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.
END OF NEW PORT CHECKLIST (delete this line) -->
* [opentelemetry-cpp] Add geneva exporter as a feature
* Initialize component path as empty list
* Update description
* Address feedback on adding comment about the design
* Generate Imath.pc
* update version
* add dependency imath minizip-ng
* updata version
* update version
* update to 1.11.0
* update version
* update
* update version
* update version
* update version
* fix missing header file
* update version
* Fix feature otlp content
* update version
* update to 1.12.0
* update version
* update version
* [opentelemetry-cpp] unvendor absl polyfills
By default opentelemetry vendors-in a copy of some Abseil polyfills
(e.g. `absl::variant`). That makes it hard (I would claim nearly
impossible) to use both the abseil and the opentelemetry-cpp ports at
the same time, as both define `absl::variant` in some of their headers.
It seems better to always use the `-DHAVE_ABSEIL=ON` CMake option and
depend on the abseil port. Outside vcpkg it may be useful to use such
vendored-in copies of the code, as that "simplifies" dependency
management. In the context of vcpkg that is just wasteful.
Simplified how to support `abseil[cxx17]` by removing some code in
opentelemetry that forcibly downgraded the compiler to use C++11. Add a
missing dependency for gRPC generated code. This code indirectly depends
on Abseil too.
* Opentelemetry is missing a find_dependency() when -DHAVE_ABSEIL=ON
* Update opentelemetry-cpp to v1.8.2
* Add feature description to otlp-http
* Update opentelemetry-cpp.json
* use ${VERSION} in portfile.cmake
* update version
---------
Co-authored-by: Lily Wang <94091114+LilyWangLL@users.noreply.github.com>
Co-authored-by: Lily Wang <494550702@qq.com>
* [opentelemetry-cpp] update opentelemetry-cpp to v1.4.1
* enable logs and metrics preview
* update versions database
* update azure-core-tracing-opentelemetry-cpp to use opentelemetry-cpp 1.4.1
* azure-core-tracing-opentelemetry-cpp: remove hard depdency on opentelemetry version instead of using 1.4.1
* Nitpick on using identical patch file.
Co-authored-by: João Soares <joao.soares@xpi.com.br>
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
* [opentelemetry-cpp] update version to v1.2.0
* [opentelemetry-cpp] update version to v1.2.0
* [opentelemetry-cpp] update version to v1.2.0
* Fix version database.
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
