doc: c++ toolchain

[junrushao]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @junrushao, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new, detailed documentation page focused on the C++ tooling within TVM-FFI. The primary goal is to provide C++ developers with clear instructions and best practices for integrating with the TVM-FFI ecosystem, covering essential aspects like header usage, CMake build system configuration, and setting up popular development environments like VSCode/Cursor and clangd. This addition aims to significantly improve the developer experience for C++ users by centralizing crucial setup and usage information.

Highlights

• New C++ Tooling Documentation: A comprehensive guide for the TVM-FFI C++ toolchain has been added, detailing header layout, CMake integration, and editor setup.
• Detailed CMake Usage: The new documentation includes in-depth explanations of CMake utilities, specifically tvm_ffi_configure_target and tvm_ffi_install functions, along with examples and guidance on setting tvm_ffi_ROOT.
• Editor Integration: Instructions for configuring VSCode/Cursor with CMake Tools and clangd are provided to enhance the C++ development workflow.
• Documentation Structure Update: The main documentation index has been updated to include the new C++ tooling guide, and a cross-reference label has been added for stub generation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces new documentation for the C++ toolchain in TVM-FFI. The added guide is comprehensive, covering header layout, CMake integration, and editor setup for VSCode and clangd. The changes are well-structured and provide valuable information for developers. I have one minor suggestion to make a code example more generic, which will improve clarity and prevent potential user errors.