Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFeatures in Mingw C++ tutorial not present in C++ extension #4840
Comments
|
Issue 3 appears to be the same as #4834 -- setting your compilerPath to the mingw compiler (or any non empty-string) should be a workaround. Not sure about issues 1 and 2. Using C/C++: Log Diagnostics with the desired file active may show what is wrong with the IntelliSense configuration. |
|
Hello, thanks for taking this up. My issue #3 was that of not finding the
expected items on the menu dropdown list. I have done what the tutorial
instructed regarding setting PATH variable to the file path of the MINGW64
compiler. That step is not in question. I am able to launch the Mingw64
console from the windows command window after setting the PATH variable.
Please confirm or correct my understanding/guess that setting the PATH
variabel is the same as what you are referring to as setting the "
compilerPath"
Thanks,
…On Mon, Jan 13, 2020 at 5:21 PM Sean McManus ***@***.***> wrote:
Issue 3 appears to be the same as #4834
<#4834> -- setting
your compilerPath to the mingw compiler should be a workaround.
Not sure about issues 1 and 2. Using C/C++: Log Diagnostics with the
desired file active may show what is wrong with the IntelliSense
configuration.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#4840?email_source=notifications&email_token=AK3EHUDOQYJ76DDIBHMHHDTQ5TSQPA5CNFSM4KGFNENKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI2QPWY#issuecomment-573900763>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK3EHUD5QOGSFRCMXKYLQRLQ5TSQPANCNFSM4KGFNENA>
.
|
|
The compilerPath is a setting in c_cpp_properties.json (from C/C++: Edit Configurations) -- which is not normally necessary to use the build and debug feature, but there's a bug that is causing the feature to fail when the compilerPath is blank. Setting the C_Cpp.default.compilerPath may also work (but I haven't verified that). The bug is causing the compilers on the PATH to not be shown in the dropdown. |
@slootmat , how did you open VS Code? Was it through a Windows command prompt? |
|
I can open VS Code in three ways:
1. from the windows command prompt after using cd to e in the folder that
the project top level was.
2. By opening a file from the VS Code GUI already opened, but without
having been opened from a VS Code workspace file.
3. By navigating to a defined VS code workspace file that I defined by
saving "Workspace as", when there was not yet a workspace file defined.
…On Tue, Jan 14, 2020 at 3:35 PM Michelle Matias ***@***.***> wrote:
g++ --version typed in fresh command prompt after setting PATH did not
recognize command, but calling the mingw64 console from that windows
command prompt did work.
@slootmat <https://github.com/slootmat> , how did you open VS Code? Was
it through a Developer Command Prompt window?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4840?email_source=notifications&email_token=AK3EHUFIKAWR4N66IFR7FE3Q5YOZ5A5CNFSM4KGFNENKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6A77Y#issuecomment-574361599>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK3EHUFDUQMXYABFGWBYZKTQ5YOZ5ANCNFSM4KGFNENA>
.
|
|
Initially I thought you'd have to open VS code from the Windows command prompt, but this is not necessary. I was able to execute As for IntelliSense not working when you right click on code sample |
Issue Type: Bug
https://code.visualstudio.com/docs/cpp/config-mingw
Version: 1.41.1 (user setup)
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362
Extension version: 0.26.2
VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:58:56.166Z)
OS version: Windows_NT x64 10.0.18362
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled