You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Contribution Steps
4
4
5
-
*[Build and debug the extension](Documentation/Getting%20started.md#build-and-debug-the-cpptools-extension).
5
+
*[Build and debug the extension](Documentation/Building%20the%20Extension.md).
6
6
* File an [issue](https://github.com/Microsoft/vscode-cpptools/issues) and a [pull request](https://github.com/Microsoft/vscode-cpptools/pulls) with the change and we will review it.
7
7
* If the change affects functionality, add a line describing the change to [**CHANGELOG.md**](Extension/CHANGELOG.md).
8
8
* Try and add a test in [**test/extension.test.ts**](Extension/test/unitTests/extension.test.ts).
Copy file name to clipboardExpand all lines: Documentation/LanguageServer/MinGW.md
+47-10Lines changed: 47 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,51 @@
1
1
For developers using MinGW on Windows, we recommend you start with the following **c_cpp_properties.json** template. Select "C/Cpp: Edit Configurations" from the command palette to create this file if you haven't already.
2
2
3
-
Note that you may have to change the MinGW version number to match what you have installed. Eg. `C:/MinGW/lib/gcc/mingw32/5.3.0/` instead of `C:/MinGW/lib/gcc/mingw32/6.3.0/`.
3
+
## With extension version 0.16.1 and higher:
4
+
5
+
Starting with version 0.16.1, if you set the `compilerPath` property and change `intelliSenseMode` to `clang-x64`, you no longer need to copy the system include path or defines to `includePath` and `defines` to enable IntelliSense to work properly. However, `browse.path` still needs to be updated manually to add the system include paths to enable code browsing for system headers. For example:
4
6
5
7
```json
6
8
{
7
9
"configurations": [
8
10
{
9
-
"name": "Win32",
11
+
"name": "MinGW",
12
+
"intelliSenseMode": "clang-x64",
13
+
"compilerPath": "C:/MinGW/bin/gcc.exe",
14
+
"includePath": [
15
+
"${workspaceFolder}"
16
+
],
17
+
"defines": [
18
+
"_DEBUG"
19
+
],
20
+
"browse": {
21
+
"path": [
22
+
"C:/MinGW/lib/gcc/mingw32/6.3.0/include",
23
+
"C:/MinGW/lib/gcc/mingw32/6.3.0/include-fixed",
24
+
"C:/MinGW/include/*",
25
+
"${workspaceFolder}"
26
+
],
27
+
"limitSymbolsToIncludedHeaders": true,
28
+
"databaseFilename": ""
29
+
},
30
+
"cStandard": "c11",
31
+
"cppStandard": "c++17"
32
+
}
33
+
],
34
+
"version": 3
35
+
}
36
+
```
37
+
38
+
Note that the `browse.path` setting is not automatically updated at this time and you may have to change the MinGW version number to match what you have installed. If you are using a different MinGW distribution, the values for `compilerPath` and `browse.path` will likely be different than what is written here.
39
+
40
+
## With extension version 0.16.0 and earlier:
41
+
42
+
In earlier versions of the extension, the `includePath` and a some system defines need to be set in order for IntelliSense to work properly. Note that you may have to change the MinGW version number to match what you have installed. Eg. `C:/MinGW/lib/gcc/mingw32/5.3.0/` instead of `C:/MinGW/lib/gcc/mingw32/6.3.0/`.
43
+
44
+
```json
45
+
{
46
+
"configurations": [
47
+
{
48
+
"name": "MinGW",
10
49
"intelliSenseMode": "clang-x64",
11
50
"includePath": [
12
51
"${workspaceRoot}",
@@ -19,15 +58,15 @@ Note that you may have to change the MinGW version number to match what you have
19
58
],
20
59
"defines": [
21
60
"_DEBUG",
22
-
"UNICODE",
23
61
"__GNUC__=6",
24
62
"__cdecl=__attribute__((__cdecl__))"
25
63
],
26
64
"browse": {
27
65
"path": [
28
66
"C:/MinGW/lib/gcc/mingw32/6.3.0/include",
29
67
"C:/MinGW/lib/gcc/mingw32/6.3.0/include-fixed",
30
-
"C:/MinGW/include/*"
68
+
"C:/MinGW/include/*",
69
+
"${workspaceRoot}"
31
70
],
32
71
"limitSymbolsToIncludedHeaders": true,
33
72
"databaseFilename": ""
@@ -37,15 +76,15 @@ Note that you may have to change the MinGW version number to match what you have
37
76
}
38
77
```
39
78
40
-
The `includePath` above includes the system header paths that gcc uses in version 6.3.0 for C++ projects and matches the output of `gcc -v -E -x c++ -`. The `intelliSenseMode` should be set to **"clang-x64"** to get MinGW projects to work properly with IntelliSense. The `__GNUC__=#` define should match the major version of the toolchain in your installation (6 in this example).
79
+
The `includePath` above includes the system header paths that gcc uses in version 6.3.0 for C++ projects and matches the output of `"gcc -v -E -x c++ nul"`. The `intelliSenseMode` should be set to **"clang-x64"** to get MinGW projects to work properly with IntelliSense. The `__GNUC__=#` define should match the major version of the toolchain in your installation (6 in this example).
41
80
42
81
For C projects, simply remove the C++ lines:
43
82
44
83
```json
45
84
{
46
85
"configurations": [
47
86
{
48
-
"name": "Win32",
87
+
"name": "MinGW",
49
88
"intelliSenseMode": "clang-x64",
50
89
"includePath": [
51
90
"${workspaceRoot}",
@@ -55,15 +94,15 @@ For C projects, simply remove the C++ lines:
55
94
],
56
95
"defines": [
57
96
"_DEBUG",
58
-
"UNICODE",
59
97
"__GNUC__=6",
60
98
"__cdecl=__attribute__((__cdecl__))"
61
99
],
62
100
"browse": {
63
101
"path": [
64
102
"C:/MinGW/lib/gcc/mingw32/6.3.0/include",
65
103
"C:/MinGW/lib/gcc/mingw32/6.3.0/include-fixed",
66
-
"C:/MinGW/include/*"
104
+
"C:/MinGW/include/*",
105
+
"${workspaceRoot}"
67
106
],
68
107
"limitSymbolsToIncludedHeaders": true,
69
108
"databaseFilename": ""
@@ -72,5 +111,3 @@ For C projects, simply remove the C++ lines:
72
111
]
73
112
}
74
113
```
75
-
76
-
With these configurations, you should be all set up to use the new IntelliSense engine for linting, memberlist autocomplete, and quick info (tooltips). Add `"C_Cpp.intelliSenseEngine": "Default"` to your **settings.json** file to try out the new IntelliSense engine.
Copy file name to clipboardExpand all lines: Documentation/LanguageServer/c_cpp_properties.json.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@
78
78
This list of paths will be used by the Tag Parser to search for headers included by your source files. The Tag Parser will automatically search all subfolders in these paths unless the path ends with a `/*` or `\*`. For example, `/usr/include` directs the Tag Parser to search the `include` folder and its subfolders for headers while `/usr/include/*` directs the Tag Parser not to look in any subfolders of `/usr/include`.
79
79
80
80
*#### `limitSymbolsToIncludedHeaders`
81
-
When true, the Tag Parser will only parse code files that have been directly or indirectly included by a source file in `${workspaceRoot}`. When false, the Tag Parser will parse all code files found in the paths specified in the **path** list.
81
+
When true, the Tag Parser will only parse code files that have been directly or indirectly included by a source file in `${workspaceFolder}`. When false, the Tag Parser will parse all code files found in the paths specified in the **path** list.
82
82
83
83
*#### `databaseFilename`
84
-
When set, this instructs the extension to save the Tag Parser's symbol database somewhere other than the workspace's default storage location. If a relative path is specified, it will be made relative to the workspace's default storage location, not the workspace folder itself. The `${workspaceRoot}` variable can be used to specify a path relative to the workspace folder (e.g. `$[workspaceRoot}/.vscode/browse.vc.db`)
84
+
When set, this instructs the extension to save the Tag Parser's symbol database somewhere other than the workspace's default storage location. If a relative path is specified, it will be made relative to the workspace's default storage location, not the workspace folder itself. The `${workspaceFolder}` variable can be used to specify a path relative to the workspace folder (e.g. `${workspaceFolder}/.vscode/browse.vc.db`)
* Add support for querying system includes/defines from WSL and Cygwin compilers. [#1845](https://github.com/Microsoft/vscode-cpptools/issues/1845), [#1736](https://github.com/Microsoft/vscode-cpptools/issues/1736)
9
+
* Fix IntelliSense for WSL projects in Windows builds 17110 and greater. [#1694](https://github.com/Microsoft/vscode-cpptools/issues/1694)
* Change file not found in `compile_commands.json` message from an error to a warning. [#1783](https://github.com/Microsoft/vscode-cpptools/issues/1783)
16
+
* Fix an IntelliSense crash during completion requests. [#1782](https://github.com/Microsoft/vscode-cpptools/issues/1782)
17
+
* Update the installed clang-format to 6.0.
18
+
* Fix bug with `compile_commands.json` when "arguments" have both a switch and a value in the arg. [#1890](https://github.com/Microsoft/vscode-cpptools/issues/1890)
19
+
* Fix bug with garbage data appearing in tooltips on Linux/Mac. [#1577](https://github.com/Microsoft/vscode-cpptools/issues/1577)
20
+
3
21
## Version 0.16.1: March 30, 2018
4
22
* Fix random deadlock caused by logging code on Linux/Mac. [#1759](https://github.com/Microsoft/vscode-cpptools/issues/1759)
5
23
* Fix compiler from `compileCommands` not being queried for includes/defines if `compilerPath` isn't set on Windows. [#1754](https://github.com/Microsoft/vscode-cpptools/issues/1754)
0 commit comments