-
Notifications
You must be signed in to change notification settings - Fork 201
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
Type std:: and other libiraries cannot be resolved #905
Comments
Do not forget to include required headers, also some important c++20 features are not implemented and you may need to change compiler standard version (like limit to |
Thanks @i-garrison . I added
under the Eclipse Preferences->Build->Settings->Discovery? I suppose this will be picked up. |
|
I saw |
Hi @ENate you need to have your c++ project properly configured, so likely yes. Could be easiest to double-check by starting from scratch and selecting e.g. managed c++ build. |
Thanks @i-garrison . So does this |
It does, yes. Make sure your source file is recognized as c++ file and all necessary headers are included and resolved (check via indexer -> search for unresolved includes.) IOW it works for me with C++17. |
Thanks indeed. This is my first experience with using Eclipse cdT for c++ development. |
Describe the bug
I am unable to access std::cout, std::string and similar C** libraries on Eclipse. When I open or create a new CMake (Makefile) project on eclipse C++, may of these libraries are not detected. I usually see the following error:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
I will expect that C++ libs and language server can automatically be picked up and code assist work normally.
Screenshots
If applicable, add screenshots to help explain your problem.
Version Information (please complete the following information):
Thanks
Additional context
Add any other context about the problem here. For example the error log (in workspace/.metadata/.log) or for GDB interaction issues the GDB traces
The text was updated successfully, but these errors were encountered: