search

microsoft / vcpkg

C++ Library Manager for Windows, Linux, and MacOS
MIT License
23.22k stars 6.4k forks source link

[GPRC C++] build failure grpcpp/generic/async_generic_service.h: No such file or directory #27732

Open yonatan555 opened 2 years ago

yonatan555 commented 2 years ago

Host Environment Linux Centos 7 , C++ gRPC installed through vcpkg. I am working on an open-source that integrated GRPC in,

To Reproduce

Steps to reproduce the behavior:

./vcpkg install gRPC

Failure logs

/root/source/opentelemetry-cpp/generated/third_party/opentelemetry-proto/opentelemetry/proto/collector/trace/v1/trace_service.grpc.pb.h:25:10: fatal error: grpcpp/generic/async_generic_service.h: No such file or directory 25 | #include <grpcpp/generic/async_generic_service.h>

This the cmake commands I ran:

cmake -DCURL_DIR=/root/vcpkg/packages/curl_x64-linux/share/curl -DCURL_LIBRARY_DIR=/root/vcpkg/packages/curl_x64-linux/lib/ -DCURL_INCLUDE_DIR=/root/vcpkg/packages/curl_x64-linux/include -DgRPC_DIR=/root/vcpkg/packages/grpc_x64-linux/include/ -Dupb_DIR=/root/vcpkg/packages/upb_x64-linux/share/upb -Dre2_DIR=/root/vcpkg/packages/re2_x64-linux/share/re2 -Dabsl_DIR=/root/vcpkg/packages/abseil_x64-linux/share/absl -Dc-ares_DIR=/root/vcpkg/packages/c-ares_x64-linux/share/c-ares -DOPENSSL_ROOT_DIR=/root/vcpkg/packages/openssl_x64-linux/share/openssl -DOPENSSL_INCLUDE_DIR=/root/vcpkg/packages/openssl_x64-linux/include/openssl -DOPENSSL_LIBRARIES=/root/vcpkg/packages/openssl_x64-linux/lib .

and the build command: cmake --build . --target all

CMakeList.cmake: in this CMaklist I included this line:

find_package(gRPC)

thanks for help

github-actions[bot] commented 1 year ago

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.

artromone commented 8 months ago

is it solved?

github-actions[bot] commented 2 months ago

This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.