otlp_grpc_metrics_exporter linker error multiple definition of absl Status kMovedFromString

[g2-aj]

Describe your environment
WSL -> Ubuntu 20.04.6 LTS
gcc version 9.4.0

Steps to reproduce
Vcpkg manifest:

{
  "dependencies": [
    {
      "name": "opentelemetry-cpp",
      "features": [
        "otlp-grpc"
      ],
      "version>=" : "1.19.0"
    }
  ],
  "builtin-baseline": "1f3f10d4911f46339411e12b1d0947c22bad5937"
}

CMakeLists.txt

find_package(opentelemetry-cpp CONFIG REQUIRED COMPONENTS)

add_executable(otlpgrpcmain
    ./src/otlpgrpcmain.cpp
)

target_link_libraries(otlpgrpcmain
    opentelemetry-cpp::otlp_grpc_metrics_exporter
)

Simple sample app:

#include "opentelemetry/exporters/otlp/otlp_grpc_metric_exporter_factory.h"
#include "opentelemetry/metrics/provider.h"
#include "opentelemetry/sdk/metrics/export/periodic_exporting_metric_reader.h"
#include "opentelemetry/sdk/metrics/meter_provider.h"

namespace otlp_exporter   = opentelemetry::exporter::otlp;
namespace metrics_api     = opentelemetry::metrics;
namespace metrics_sdk     = opentelemetry::sdk::metrics;

int main(int argc, char** argv)
{
    std::shared_ptr<metrics_api::MeterProvider> apiProvider;

    otlp_exporter::OtlpGrpcMetricExporterOptions options;
    options.endpoint = "collector-endpoint:4317";
    std::unique_ptr<metrics_sdk::PushMetricExporter> exporter = otlp_exporter::OtlpGrpcMetricExporterFactory::Create(options);

    // Initialize and set the MeterProvider
    metrics_sdk::PeriodicExportingMetricReaderOptions reader_options;
    std::unique_ptr<metrics_sdk::MetricReader>        reader = std::make_unique<metrics_sdk::PeriodicExportingMetricReader>(std::move(exporter), reader_options);

    apiProvider      = std::make_shared<metrics_sdk::MeterProvider>();
    auto sdkProvider = std::static_pointer_cast<metrics_sdk::MeterProvider>(apiProvider);
    sdkProvider->AddMetricReader(std::move(reader));

    return 0;
}

What is the expected behavior?
Expect to compile and link succesfully

What is the actual behavior?
Linker error:
[100%] Linking CXX executable otlpgrpcmain
/usr/bin/ld: vcpkg_installed/x64-linux/debug/lib/libabsl_status.a(status.cc.o):(.rodata+0x320): multiple definition of `absl::lts_20240722::Status::kMovedFromString'; vcpkg_installed/x64-linux/debug/lib/libgrpc.a(client_channel_service_config.cc.o):(.rodata._ZN4absl12lts_202407226Status16kMovedFromStringE[_ZN4absl12lts_202407226Status16kMovedFromStringE]+0x0): first defined here
collect2: error: ld returned 1 exit status

Additional context
N/A

[dbarker]

One issue may be that the vcpkg portfile for opentelemetry-cpp is turning on WITH_ABSEIL here, which will link it to the api. The version linked likely does not match the version that is used by grpc.

A fix may be to remove the WITH_ABSEIL=ON, this should not be needed in most cases. See #3116 for detailed discussion and proposal for deprecation.

Fixing this may also require pinning compatible versions of abseil, protobuf, and grpc in the opentelemetry-cpp portfile. More recent versions of Protobuf also depend on abseil. For reference please see the compatible versions defined in the development Dockerfile. These versions are also tested in ci.

[g2-aj]

Update: for my WSL environment specified above I was able to get this to build by ensuring vcpkg was building with C++17
Not sure if all the following were needed but this is what I added and after this I did not see the linker error anymore.

set(VCPKG_TARGET_TRIPLET x64-linux)
set(VCPKG_CXX_FLAGS "-std=c++17")
set(VCPKG_CXX_FLAGS_RELEASE "-std=c++17")
set(VCPKG_CXX_FLAGS_DEBUG "-std=c++17")
set(VCPKG_C_FLAGS "-std=c++17")
set(VCPKG_C_FLAGS_DEBUG "-std=c++17")
set(VCPKG_C_FLAGS_RELEASE "-std=c++17")

However, the next issue I hit was during cross compile for aarch64 target. The issue here is that the version of abseil opentelemetry uses in vcpkg injects x86_64 compiler options which are unknown to aarch64.
See more information about this issue here: abseil/abseil-cpp#1241
This could be fixed using this patch
However, I could not figure out how to apply this patch in vcpkg manifest mode which is what I need for my build pipeline.