error MSB6006: “CL.exe” exited with code 2

Question

I\'m writing with visual c++ and when I compile this error occures:

C:\\Program Files (x86)\\MSBuild\\Microsoft.Cpp\\v4.0\\Platforms\\Win32\\Microsoft.Cpp.Wi         


        

Answer 1

I get this bug in v110 (Visual studio 2012)-Compiler with the following code, which contains a wrong for-based loop.

class A
{
    int b;
};

int main(int argc, char* argv[])
{
    A inst;

    for (auto &i : inst)
    {

    }

    return 0;
}

PS: v140 (Visual Studio 2015) shows the correct error:

error C3312: no callable 'begin' function found for type 'A'
error C3312: no callable 'end' function found for type 'A'

Answer 2

Could also be an actually deleted header or source file, still listed in your project. Just check for such files.

I deleted a Header and Source file using the system explorer. VS apparently doesn't recognize the absence of deleted files and tries to compile them, till you reload your project.

Reloading the project worked for me.

Answer 3

I got this error because I had misspelled a filename when I save it.* Incidentally, this save was after having inserted a few for loops, which sent me on a wild goose chase because those can be a source of this error as well.

Sahbi's tip to look at the Output tab instead of just the general Error Code tab was very useful to me! I used the View menu to find and display the Output tab. It read the following:

1>------ Build started: Project: C867 Performative Assessment, Configuration: Debug x64 ------ 1>Security_Student.cpp 1>c1xx: fatal error C1083: Cannot open source file: 'Security_Student.cpp': No such file or directory 1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(429,5): error MSB6006: "CL.exe" exited with code 2. 1>Done building project "C867 Performative Assessment.vcxproj" -- FAILED. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

I had saved the file as 'Securtiy_Student.cpp'.*

I'd comment and upvote, but I don't have the rep yet.

*This wouldn't have been a problem if the correctly spelled file had not also been deleted, because the compiler would have just ignored the misspelled file and used the previous version that was spelled correctly. However, I'm also getting a weird bug with Visual Studio where it will occasionally decide that one of my files is new when I try to save it and must "Save as..." But, then when I accept that action, it says the file already exists, but if I try to replace it with the save, it says you can't replace it because it's being used. So, the solution has been to paste the file into a text file, decline to save the file in the Visual Studio solution, erase the solution file, create a new file, paste the text into it, and save into the solution again. Anyway, I will post this problem elsewhere, but I wanted to give context for a sneaky way one could get the error in this thread from a misspelled filename.