vcpkg/ports/opentelemetry-cpp/vcpkg.json
Carlos O'Ryan 43401f5835
[opentelemetry-cpp] unvendor absl polyfills (#30720)
* [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
2023-04-10 12:50:22 -07:00

71 lines
1.9 KiB
JSON

{
"$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
"name": "opentelemetry-cpp",
"version-semver": "1.8.3",
"port-version": 3,
"description": [
"OpenTelemetry is a collection of tools, APIs, and SDKs.",
"You use it to instrument, generate, collect, and export telemetry data (metrics, logs, and traces) for analysis in order to understand your software's performance and behavior."
],
"homepage": "https://github.com/open-telemetry/opentelemetry-cpp",
"license": "Apache-2.0",
"dependencies": [
"abseil",
"curl",
"nlohmann-json",
{
"name": "vcpkg-cmake",
"host": true
},
{
"name": "vcpkg-cmake-config",
"host": true
}
],
"features": {
"elasticsearch": {
"description": "Whether to include the Elasticsearch Client in the SDK"
},
"etw": {
"description": "Whether to include the ETW Exporter in the SDK",
"supports": "windows"
},
"jaeger": {
"description": "Whether to include the Jaeger exporter",
"dependencies": [
"thrift"
]
},
"otlp": {
"description": "Whether to include the OpenTelemetry Protocol in the SDK",
"dependencies": [
"grpc",
{
"name": "grpc",
"host": true
},
"protobuf"
]
},
"otlp-http": {
"description": "Whether to include the OpenTelemetry Protocol over HTTP in the SDK",
"dependencies": [
"curl",
"protobuf"
]
},
"prometheus": {
"description": "Whether to include the Prometheus Client in the SDK",
"dependencies": [
"prometheus-cpp"
]
},
"zipkin": {
"description": "Whether to include the Zipkin exporter in the SDK"
},
"zpages": {
"description": "Whether to include the Zpages Server in the SDK"
}
}
}