Menu
Learn more about.
This update is recommended for all DVD Studio Pro 4.2 users. What’s New in this Version DVD Studio Pro 4.2.1 addresses specific customer issues, compatibility issues, and general performance issues and improves overall stability.
![Dvd studio pro download for mac Dvd studio pro download for mac](/uploads/1/2/4/8/124813281/242155047.jpg)
![Configure Launch.json Visual Studio Code For Mac C++ Configure Launch.json Visual Studio Code For Mac C++](/uploads/1/2/4/8/124813281/825454925.png)
![Visual studio code for chromebook Visual studio code for chromebook](https://msdnshared.blob.core.windows.net/media/2016/08/aug1.png)
Visual Studio for Mac.NET. Azure DevOps. 0 [c++] Default launch.vs.json configuration keeps being added to the configurations array. Windows 10.0 visual studio 2017 rc. Edit the configuration name. Repeat Step 2. Expected: The user is taken to the edited configuration. Yeah, Visual Studio Code is quite interesting for cross platform C++ development. Just a note for people not familiar with VS Code: The C++ plugin is in active development.
How have you been developing Chromium? I have often been asked what is the best tool to develop Chromium. I guess Chromium developers have been usually using vim, emacs, cscope, sublime text, eclipse, etc. And they have used GDB or console logs for debugging. But, in case of Windows, developers have used Visual Studio. Although Visual Studio supports powerful features to develop C/C++ programs, unfortunately, it couldn’t be used by other platform developers. However, recently I notice that Visual Studio Code also can support to develop Chromium with the nice editor, powerful debugging tools, and a lot of extensions. And, even it can work on Linux and Mac because it is based on Electron. Nowadays I’m developing Chromium with VS Code. I feel that VS Code is one of the very nice tools to develop Chromium. So I’d like to share my experience how to develop Chromium by using the Visual Studio Code on Ubuntu.
* https://chromium.googlesource.com/chromium/src/+/lkcr/docs/vscode.md
- Download VS Code
- Launch VS Code in chromium/src
- Install useful extensions
- Python – Linting, intellisense, code formatting, refactoring, debugging, snippets.
- c/c++ for visual studio code – Code formatting, debugging, Intellisense.
- Toggle Header/Source – Toggles between .cc and .h with
F4
. The C/C++ extension supports this as well throughAlt+O
but sometimes chooses the wrong file when there are multiple files in the workspace that have the same name. - you-complete-me – YouCompleteMe code completion for VS Code. It works fairly well in Chromium. To install You-Complete-Me, enter these commands in a terminal:
- Rewrap – Wrap lines at 80 characters with
Alt+Q
.
- Setup for Chromium
- Chromium added the default settings files for vscode. We can move them to //src/.vscode folder.
- Workspace setting
– https://cs.chromium.org/chromium/src/tools/vscode/settings.json5 - Task setting
– https://cs.chromium.org/chromium/src/tools/vscode/tasks.json5 - Launch setting
– https://cs.chromium.org/chromium/src/tools/vscode/launch.json5
- Workspace setting
- Chromium added the default settings files for vscode. We can move them to //src/.vscode folder.
- Key mapping
- (Optional) Color setting
- Press
Ctrl+Shift+P, color, Enter
to pick a color scheme for the editor
- Press
- Set workspaceRoot to .bashrc. (Because it will be needed for some extensions.)
- Copy 3 settings files from //src/tools/vscode to //src/.vscode
- You can find my configuration files based on the default files
- Set ycmd path to .vscode/settings.json
- Add new tasks to tasks.json in order to build Chromium by using ICECC.
- I wrote a post about how to build Chromium by using ICECC in the previous post. Please setup it first.
- Add buildChromiumICECC.sh Debug to the tasks.json
- Update “Chrome Debug” configuration in launch.json
you will see this window after finishing all settings.
- Run Task (Menu -> Terminal -> Run Tasks…)
- Select 1-build_chrome_debug_icecc. VS Code will show an integrated terminal when building Chromium as below, On the ICECC monitor, you can see that VS Code builds Chromium by using ICECC.
After completing the build, now is time to start debugging Chromium.
- Set a breakpoint
- F9 button or just click the left side of line number
- Launch debug
- Press F5 button
- Screen captures when debugger stopped at a breakpoint
- Overview
- Editor
- Call stack
- Variables
- Watch
- Breakpoints
- Overview
Todo
In multiple processes model, VS Code can’t debug child processes yet (i.e. renderer process). According to C/C++ extension project site, they suggested us to add the below command to launch.json though, it didn’t work for Chromium when I tried.
How To Use Visual Studio Code For C++
Reference
- Chromium VS Code setup: https://chromium.googlesource.com/chromium/src/+/lkcr/docs/vscode.md