In file included from /Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX13.3.sdk/usr/include/c++/v1/iostream:41: clangĮrror: In file included from src/main.cpp:1: 13.3Ĭheckinfo: cannot runv(zig version), No such file or directoryĬhecking for /Library/Developer/CommandLineTools/usr/bin/clang. 13.3Ĭhecking for Minimal target version of Xcode for macosx (arm64). noĬhecking for SDK version of Xcode for macosx (arm64).
Applications/Xcode.appĬhecking for Codesign Identity of Xcode. I am going to cleanup my paths from some bad “Google advice” and try again.Ĭhecking for Xcode directory. No response Additional Information and Error Logs But, that doesn't make sense in c++ where we need to explicitly encode as utf-8 as in: cout << u8"\033[2J" So, it can't be the compiler mis-interpreting string constants. Could be that visual studio code natively uses utf-8, so string constants could look like there made of wchar's. Expected BehaviorĬlang++ should do its job without messing up over a header file that's not even being requested in the project. In another project, a single cpp file of 1300 lines builds and runs perfectly. There is something strange with commandlinetools going on.
0 kommentar(er)
