[google-cloud-cpp] Add recipe for Google Cloud Services

[jgsogo]

Specify library name and version: google-cloud-cpp/1.26.1

Pushing this recipe, so we can use C++ to create GCP microservices... for ConanCenter itself 🤔

This recipe requires:

• crc32c: [crc32c] Add new recipe #5395
• gRPC changes: [grpc] Use build_modules to find executable grpc_cpp_plugin #5404
• There is also one ExternalProject_Add here: googleapis, using it will require patching these sources, and it doesn't offer tags/releases. I'll add that that reference later.

Also, I will rebase/squash this PR once dependencies are merged.

close #5212

[prince-chrismc]

I think my comment will break... but it's a minor detail

✔️

[conan-center-bot]

All green in build 19 (38c006dfd00d22501be52bba8f8c178b281d0ffa):

• google-cloud-cpp/1.26.1@:
  All packages built successfully! (All logs)

[danimtb]

If this configuration is not working, why adding set(CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS ON) in CMakeLists.txt?

[jgsogo]

Well... I tried to too, and probably it is possible, but without a local Windows to test and try I gave up. Also, it will probably build for older VS versions... Someone will take care in another PR if needed 😊

[SpaceIm]

Looking at installed pkgconfig files, pkg_config files are not properly emulated. This component google-cloud-common could have been called common with pkgconfig name google_cloud_cpp_common.

CMake targets seem ok, but generators can't emulate official config files, and google-cloud-cpp generates more than one config file.
Actually, there is no google-cloud-cpp-config.cmake file upstream.

[jgsogo]

I find your suggestion much more convenient. From the consumer perspective, I prefer to use google-cloud-cpp::common over google-cloud-cpp::google-cloud-common to refer to that component. I think it is worth a PR and probably a suggestion to follow for other PRs, wdyt @prince-chrismc ?

[prince-chrismc]

From the CMake perspective google-cloud-cpp::common should be working since we added those names 🤔 both names are currently available AFAIK.

My original comment stems for all the times Space flagged this potential issue, I did not check the pkg_config log but we could have done the inverse as is suggested. So I have no objections here.

Instead of changing the component name we could simple just add the corrected name? Avoid changing it's usage in the recipe

self.cpp_info.components["google-cloud-common"].names["pkg_config"] = "google_cloud_cpp_common"

I assume they did not use "common" since it was too common xD

[jgsogo]

My comment was about Conan components, not related to CMake targets. From a consumer package you will refer to that component as google-cloud-cpp::google-cloud-common (now). I'm voting to changing it back to google-cloud-cpp::common.

CMake targets are not changed. Pkgconfig would require the line you suggested.