#include <iostream> is unrecognized

[livid fjord]

I use VS code. Once I launched new file it started happening everywhere. g++ is okay

[valid moon]

When your question is answered use !solved or the button below to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question use !howto ask.

@livid fjord

Screenshots!

Your message appears to contain screenshots but no code. Please send code and error messages in text instead of screenshots if applicable!

[livid fjord]

#include errors detected. Please update your includePath. Squiggles are disabled for this translation unit (D:\cpp\practice\oparisi\main.cpp).
could not open source file "iostream" (no directories in search list). Please run the 'Select IntelliSense Configuration...' command to locate your system headers.

[limber blaze]

1. show your c_cpp settings
2. Does it compile?

[livid fjord]

    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE"
            ],
            "compilerPath": "cl.exe",
            "cStandard": "c23",
            "cppStandard": "c++26",
            "intelliSenseMode": "windows-msvc-x64"
        }
    ],
    "version": 4
}```
The terminal process "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command g++ -g 'D:\cpp\practice\oparisi\main.cpp' -o 'D:\cpp\practice\oparisi/main.exe'" terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

[last tree]

Are you using msys2?

[livid fjord]

Is that gcc? I use it

[limber blaze]

I would strongly suggest changing the default terminal from powershell to cmd. It tends to cause issues down the road

also why dont you use VisualStudio instead?

[livid fjord]

I used Visual studio, but I like vscode more

[limber blaze]

Open your command prompt and type in where cl.exe. Then paste the output

[livid fjord]

I think I dont have cl.exe, it answered nothing

[last tree]

Huh. What kind of issues?

[last tree]

How did you install gcc?

[limber blaze]

if you wish to use cl.exe (msvc) then you need to install MSVC toolchain first and add it to path

[livid fjord]

At least it shows gcc and g++ versions

[last tree]

Tbh I wouldn't bother with MSVC. Its only redeeming quality is being shipped with VS by default. If I had to choose a compiler, I'd go for Clang

[livid fjord]

And when I type in cl --version it gives me version

[last tree]

Ok, how did you install them?

[limber blaze]

If you use github copilot then any command will be in a form of a powershell commands. Which then causes issues as its syntax mixes with cmd prompt making it all crash.

It also has issues by itself with args. Dunno if they fixed it already but I wouldnt bet on that.

[livid fjord]

Frod VisualStudio build tools 2022

[limber blaze]

so where cl.exe doesnt show anything but cl --version does...?

[last tree]

Those surely don't ship GCC 😛

[livid fjord]

Yes

[last tree]

What exactly does where cl.exe show?

[livid fjord]

Just silence

[limber blaze]

can you send a screenshot?

[last tree]

huh

Try gcm cl.exe

[limber blaze]

yet another powershell issue

[last tree]

I have a tutorial on seting up VSC with Clang or GCC here: https://github.com/HolyBlackCat/cpp-tutorials
If you need that

[livid fjord]

This what I get from x64 Native tools...

[last tree]

Ok. Does gcm cl.exe work in VSC terminal?

[livid fjord]

-----------     ----                                               -------    ------
Application     cl.exe                                             14.44.3... C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\cl.exe```

[last tree]

Aha. So it's just where not working in powershell

@limber blaze What were you planning to do with the CL path 😛

[limber blaze]

Just a habit of checking whenever its in a PATH

but I guess if its in the path then cl.exe is fine

[livid fjord]

Path is alright. I added every complier and interpretator I need

[last tree]

So you do use msys2

Then my recommendation would be to install mingw-w64-x86_64-clang-tools-extra in it, and install the Clangd extension in VSC. This replaces the stock intellsense with the Clangd one, which should be better in general

And should find your headers out of the box

[livid fjord]

Ill try this tomorrow and write back here

[livid fjord]

Thank you so much guys, it started working

!solved