Tracking issues of cpp binding

[silver-ymz]

Tasks

• Introducing new cpp binding feat(bindings/cpp): init cpp binding #2980
• Add Contribution docs docs(bindings/cpp): add CONTRIBUTING.md  #2984
• Add API documents docs(bindings/cpp): use doxygen to generate API docs #2988
• Add CI jobs on building and testing ci(bindings/cpp): add ci for test and doc #2998
• Support more operations
  • feat(bindings/cpp): expose all api returned by value #3001
  • feat(bindings/cpp): expose reader  #3004
  • feat(bindings/cpp): expose lister #3011
• Release first version
• Tracking Issue: Async support for C++ binding #5194
• Add layer supports

[Xuanwo]

I am excited about the upcoming iostream and async support. I anticipate being able to utilize cpp binding in critical projects such as clickhouse, doris, and nebula (cc @wey-gu).

[silver-ymz]

cpp binding now uses some unreleased API in v0.39, e.g. list and lister. Should we pin the version of opendal to 0.39 in cpp binding, make the first release and then revert back to current implementation?

[Xuanwo]

Should we pin the version of opendal to 0.39 in cpp binding, make the first release and then revert back to current implementation?

No, we will release all projects under opendal at the same version.

[Xuanwo]

By the way, when you mention releasing the cpp binding, what exactly do you mean? Are you referring to packaging our cpp binding and making it available in a registry?

[silver-ymz]

By the way, when you mention releasing the cpp binding, what exactly do you mean?

Because CMakeLists.txt isn't in the root directory of project, we need to use cargo package to create a opendal-cpp.tar.gz individually in github release assets. This allows our users to import directly via cmake FetchContent without having to download and write additional cmake scripts.

Are you referring to packaging our cpp binding and making it available in a registry?

Cpp seems to have no central registers. About integrating with other popular package management like conan, vcpkg, we can complete it in the future.

[Xuanwo]

This allows our users to import directly via cmake FetchContent without having to download and write additional cmake scripts.

Got it.

Cpp seems to have no central registers. About integrating with other popular package management like conan, vcpkg, we can complete it in the future.

LGTM.

---

Please be aware that in ASF, release is a crucial matter and all our releases must undergo the voting process. So we can't simply tag a v0.1 for cpp binding and put them in github assets.

To reduce the burden of our release mangaers, it's better to tag the same version for all our projects and release them after the voting.

Our next release windows is opendal v0.40 which expected to happen this week.