-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"#include errors detected. Consider updating..." && "cannot open source file "initializer_list" | Unexpected Intellisense errors occuring on v1.22.11 in Unreal project #12940
Comments
@ChrisLFieldsII I'm seeing the C++ system include paths from clang++ being missing and only these.
e.g. not /Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/usr/include/c++/v1 Can you confirm that 1.18.5 shows the additional c++ system includes in the Log Diagnostics output? Also, it sounds like you're saying the bug repros with 1.19.9 as well? With 1.22.11, with C_Cpp.loggingLevel set to "Debug" do you see any error messages related to quering clang++ in the "C++" logging pane? Can you provide the output of running ...but 1.19.9 was released in March and so far I've only seen 1 other Unreal Engine user report this issue with 1.19.4 in #12049 . |
@sean-mcmanus I see that as well now, great eyes! I am attaching the Log Diagnostics from version I believe you are referring to I switched to this version and have the same issue reported in |
@ChrisLFieldsII It looks like the bug is caused by -isysroot not being applied to the mac Framework. |
@sean-mcmanus I gotcha. That makes sense. I completely forgot to post the results of running the command you wanted me to. It did have an error Attaching a pic & text of the results in case that helps.
|
It's a regression from https://github.com/microsoft/vscode-cpptools/releases/tag/v1.19.3 (doesn't repro with 1.19.2) from internal PR 524107 -- but it sounds like it was a "by design" change such that the compilerArgs from the compile_commands.json are used instead of the compilerArgs from c_cpp_properties.json, so your @ChrisLFieldsII I'm guessing @ChrisLFieldsII Are you able to fix it such that -isystem is used in the compile_commands.json/.rsp files? i.e. maybe file a bug on Unreal? |
@ChrisLFieldsII #11889 suggests we could add a new property to c_cpp_properties.json to get the <1.19.2 behavior -- would you be able set that new property or are the compilerPath/compilerArgs being generated/overwritten by the Unreal tools? We might also be able to add a C_Cpp. setting instead to configure the behavior. |
@sean-mcmanus I see, #11889 does seem to indicate the issue which is the @sean-mcmanus I looked through #11889 and did not see the potential property you referenced so I was not able to try that Here is what the compileCommands_Default.json looked like which UE generated and causes the reported issue
Here is what I updated compileCommands_Default.json to which resolved the reported issue on version 1.22.11 of the extension by ensuring each command passes the `-isysroot` flag
I could potentially file a bug against UE for the Here is the CharacterMovement.1.rsp for the record. It does not include the `-isysroot`
|
@ChrisLFieldsII Yeah, I think getting Unreal to add |
@ChrisLFieldsII The We can look into filing a bug on Unreal Engine (or you could). They've fixed configuration generation issues for us in the past. Also, in case you didn't know, Visual Studio 2022 has a bunch of Unreal Engine specific features that aren't in VS Code so that is generally recommended for those projects: https://learn.microsoft.com/en-us/visualstudio/gamedev/unreal/get-started/vs-tools-unreal-overview, https://devblogs.microsoft.com/cppblog/unreal-engine-cpp-game-development-made-easy-visual-studio-2022/ |
@sean-mcmanus Ok got it, that all makes sense to me including the fix being the Unreal generated That would be awesome if someone more educated with the extension filed the bug on Unreal Engine. I'm still fairly new to UE and C++ 😅 Sweet, I'll have to check out Visual Studio 2022 on my Windows machine. I didn't know about some of the extra features it has |
@ChrisLFieldsII Sure, we've contacted the Unreal Engine team. |
Environment
If using SSH remote, specify OS of remote machine:Bug Summary and Steps to Reproduce
Bug Summary:
Intellisense displays error on Unreal Engine 5 C++ files stating source files could not be opened.
This ticket is pretty much a copy of #12049 as those issues were never solved and closed since no information was provided. I would be happy to provide any help to get this resolved or open a ticket elsewhere if that is deemed appropriate.
Steps to reproduce:
Expected behavior:
These errors do not show when opening Unreal source code in VSC. Downgrading this extension to version 1.18.5 does not have this issue and is my current workaround.
Configuration and Logs
I attached these logs as files in the "additional context" section as they exceeded the character limit
Other Extensions
Retrieved via
code --list-extensions
artdiniz.quitcontrol-vscode
cssho.vscode-svgviewer
dbaeumer.vscode-eslint
eamodio.gitlens
esbenp.prettier-vscode
exodiusstudios.comment-anchors
expo.vscode-expo-tools
formulahendry.auto-close-tag
formulahendry.auto-rename-tag
github.copilot
github.copilot-chat
github.github-vscode-theme
graphql.vscode-graphql
graphql.vscode-graphql-execution
graphql.vscode-graphql-syntax
gruntfuggly.todo-tree
mikestead.dotenv
ms-azuretools.vscode-docker
ms-dotnettools.csdevkit
ms-dotnettools.csharp
ms-dotnettools.vscode-dotnet-runtime
ms-dotnettools.vscodeintellicode-csharp
ms-vscode.cpptools
ms-vsliveshare.vsliveshare
msjsdiag.vscode-react-native
naco-siren.gradle-language
naumovs.color-highlight
pkief.material-icon-theme
prisma.prisma
streetsidesoftware.code-spell-checker
sysoev.vscode-open-in-github
tomoki1207.pdf
visualstudiotoolsforunity.vstuc
vsls-contrib.gistfs
wallabyjs.quokka-vscode
wix.vscode-import-cost
wware.snippet-creator
xaver.clang-format
yoavbls.pretty-ts-errors
Additional context
language-server-logging.txt
c_cpp_properties.json
log-diagnostics.txt
The text was updated successfully, but these errors were encountered: