Windows下VS Code配置Chromium代码自动补全遇问题求助

Hey there, let’s work through your auto-completion issue with Chromium, VS Code, and You-Complete-Me (YCM) on Windows. First, we’ll debug your existing configuration, then I’ll share a streamlined setup guide to get you up and running smoothly.

Part 1: Fixing Your Current Configuration #

Let’s go through each step you took and spot potential issues:

1. YCM Path Configuration Issue #

Your ycmd.path uses ~ in the Windows path:

"ycmd.path": "C:/Program Files/~/.ycmd"

The ~ shortcut doesn’t work in Windows file paths—it’s a Unix/Linux convention. Replace this with your actual user directory path, e.g.:

"ycmd.path": "C:/Users/YourUsername/.ycmd"

Double-check that this directory exists and contains the compiled YCM core files (YCM requires manual compilation for Windows MSVC support; pre-built versions often fail here).

2. Verify chromium.ycm_extra_conf.py Path #

Your current path points to D:/chromium/depot_tools/src/tools/vim/chromium.ycm_extra_conf.py—this is likely incorrect. The Chromium YCM config file lives in the Chromium source root, not inside depot_tools. If your Chromium source is in D:/chromium/src, the correct path should be:

"ycmd.global_extra_config":"D:/chromium/src/tools/vim/chromium.ycm_extra_conf.py"

Confirm the file exists at this location before proceeding.

3. Fix compile_commands.json Path & Content #

• Ensure you ran the ninja command from the Chromium source root directory (not depot_tools). If you ran it elsewhere, the paths inside compile_commands.json will be relative and invalid for YCM.
• Open out/Default/compile_commands.json and check if all file paths are absolute. Ninja often generates relative paths on Windows, which YCM can’t resolve. Use a quick Python script to replace relative paths with absolute ones:

  import json
  import os
  
  with open('out/Default/compile_commands.json', 'r') as f:
      data = json.load(f)
  root_dir = os.path.abspath('.')
  for entry in data:
      entry['file'] = os.path.join(root_dir, entry['file'])
  with open('out/Default/compile_commands.json', 'w') as f:
      json.dump(data, f, indent=2)
  

  Run this script from your Chromium source root to fix the paths.

4. Validate c_cpp_properties.json #

• Ensure ${workSpaceRoot} points to your Chromium source root. If you opened VS Code to D:/chromium/depot_tools instead of D:/chromium/src, this variable will be wrong—reopen VS Code directly on the source root.
• Check that your Visual Studio version matches Chromium’s requirements. As of 2024, Chromium requires Visual Studio 2022 (not 2017) for Windows builds. Using an older VS version can break IntelliSense and YCM integration.

Part 2: Streamlined VS Code Chromium Development Guide (Windows) #

If you want to avoid YCM’s Windows quirks, the official C/C++ Extension Pack is more reliable. Here’s a step-by-step setup:

1. Prerequisites #

• Install Visual Studio 2022 with the Desktop development with C++ workload, plus the matching Windows SDK version (check Chromium’s official docs for the exact required version).
• Set up depot_tools, add it to your system PATH, and sync the Chromium source code via gclient sync.
• Generate build files with GN:

  gn gen out/Default --args="is_debug=true target_cpu=\"x64\""
  

2. Install Extensions #

Install the C/C++ Extension Pack from the VS Code Marketplace—it includes all tools needed for C++ IntelliSense, debugging, and formatting.

3. Configure IntelliSense #

• Generate a valid compile_commands.json (run from Chromium source root):

  ninja -C out/Default -t compdb cc cxx objc objcxx > out/Default/compile_commands.json
  

• Fix relative paths with the Python script mentioned earlier.
• Open VS Code to your Chromium source root, press Ctrl+Shift+P, select C/C++: Edit Configurations (UI):
  • Compiler Path: Point to your VS 2022 cl.exe, e.g., C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.38.33130/bin/Hostx64/x64/cl.exe
  • Compile Commands: Select the absolute path to out/Default/compile_commands.json
  • IntelliSense Mode: Choose msvc-x64

4. Test Auto-Completion #

Open a core Chromium file like base/logging.h, type LOG(—you should see auto-completion suggestions for logging macros. If not, run C/C++: Reset IntelliSense Database via the command palette to clear cached data.

Part 3: Additional Tips for YCM Users #

If you still want to use YCM:

• Compile YCM from source on Windows, ensuring you enable MSVC support during the build process (follow YCM’s official Windows compilation guide closely).
• Check the YCM output log in VS Code (go to View > Output > Select "You-Complete-Me") for error messages—this will tell you if YCM can’t find the ycmd server, load the config file, or parse compile_commands.json.

内容的提问来源于stack exchange，提问作者Justin