Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » Multiple "could not be resolved" problems
Multiple "could not be resolved" problems [message #1797548] Thu, 01 November 2018 16:21 Go to next message
Eclipse UserFriend
I have recently installed (the latest builds of) 'Eclipse IDE for C/C++ Developers' and minGW to help me to get back into C++ after a long time away.

I have added "-std=c++11" to "Other flags" at C/C++ Build/Settings/Tool Settings/GCC C++ Compiler/Miscellaneous

I have a small program utilising a number of C++11 features (e.g. using the chrono library, .emplace_back).
VidMate AnyDesk mobdro.onl/

After Run I get multiple unresolved issues in the Problems window, as Pasted below).

Interestingly, the program does compile and run ok.

1) With this, is there something I'm not setting up in Eclipse to resolve these issues?

2) While it might not apply to this forum, is there still an issue with the 'to_string()' function e.g. the following extract does not compile:

window.setTitle("Bullets on screen: " + to_string(bullets.size()) + " currentSlice: " + to_string(currentSlice) + " FT: " + to_string(ft) + " FPS: " + to_string(fps));


Thanks.



Description Resource Path Location Type
Symbol 'duration' could not be resolved chronotest.cpp /chronotest/src line 19 Semantic Error
Function 'now' could not be resolved Test2.cpp /Test2/src line 143 Semantic Error
Function 'duration_cast' could not be resolved Test2.cpp /Test2/src line 160 Semantic Error
Function 'now' could not be resolved Test2.cpp /Test2/src line 158 Semantic Error
Symbol 'chrono' could not be resolved Test2.cpp /Test2/src line 8 Semantic Error
Type 'std::centi' could not be resolved chronotest.cpp /chronotest/src line 20 Semantic Error
Type 'std::chrono::seconds' could not be resolved chronotest.cpp /chronotest/src line 24 Semantic Error
Type 'std::time_t' could not be resolved chronotest.cpp /chronotest/src line 48 Semantic Error
Symbol 'duration' could not be resolved chronotest.cpp /chronotest/src line 47 Semantic Error
Function 'now' could not be resolved chronotest.cpp /chronotest/src line 44 Semantic Error
Function 'now' could not be resolved chronotest.cpp /chronotest/src line 39 Semantic Error
Type 'std::chrono::system_clock' could not be resolved chronotest.cpp /chronotest/src line 38 Semantic Error
Function 'end' could not be resolved Test2.cpp /Test2/src line 214 Semantic Error
Symbol 'time_point' could not be resolved chronotest.cpp /chronotest/src line 38 Semantic Error
Function 'end' could not be resolved Test2.cpp /Test2/src line 212 Semantic Error
Type 'milli' could not be resolved Test2.cpp /Test2/src line 161 Semantic Error
Method 'count' could not be resolved Test2.cpp /Test2/src line 161 Semantic Error
Symbol 'duration_cast' could not be resolved Test2.cpp /Test2/src line 160 Semantic Error
Symbol 'duration' could not be resolved Test2.cpp /Test2/src line 161 Semantic Error
Method 'count' could not be resolved chronotest.cpp /chronotest/src line 51 Semantic Error
Symbol 'duration_cast' could not be resolved chronotest.cpp /chronotest/src line 30 Semantic Error
Method 'count' could not be resolved chronotest.cpp /chronotest/src line 30 Semantic Error
Function 'to_time_t' could not be resolved chronotest.cpp /chronotest/src line 48 Semantic Error
Method 'count' could not be resolved chronotest.cpp /chronotest/src line 32 Semantic Error
Function 'ctime' could not be resolved chronotest.cpp /chronotest/src line 50 Semantic Error
Method 'count' could not be resolved chronotest.cpp /chronotest/src line 33 Semantic Error
Symbol 'duration' could not be resolved chronotest.cpp /chronotest/src line 22 Semantic Error
Invalid arguments '
Candidates are:
__gnu_cxx::__normal_iterator<Bullet *,std::vector<Bullet,std

[Updated on: Sun, 04 November 2018 19:01] by Moderator

Report message to a moderator

Re: Multiple "could not be resolved" problems [message #1816223 is a reply to message #1797548] Thu, 24 October 2019 09:59 Go to previous messageGo to next message
Mohsin Memon is currently offline Mohsin MemonFriend
Messages: 1
Registered: October 2019
Junior Member
have recently installed (the latest builds of) 'Eclipse IDE for C/C++ Developers' and minGW to help me to get back into C++ after a long time away.

I have added "-std=c++11" to "Other flags" at C/C++ Build/Settings/Tool Settings/GCC C++ Compiler/Miscellaneous

I have a small program utilising a number of C++11 features (e.g. using the chrono library, .emplace_back).
VidMate AnyDesk mobdro.onl/

After Run I get multiple unresolved issues in the Problems window, as Pasted below).

Interestingly, the program does compile and run ok.

1) With this, is there something I'm not setting up in Eclipse to resolve these issues?

2) While it might not apply to this forum, is there still an issue with the 'to_string()' function e.g. the following extract does not compile:

window.setTitle("Bullets on screen: " + to_string(bullets.size()) + " currentSlice: " + to_string(currentSlice) + " FT: " + to_string(ft) + " FPS: " + to_string(fps));

Cheers,
Mohsin Memon
Re: Multiple "could not be resolved" problems [message #1816408 is a reply to message #1816223] Tue, 29 October 2019 07:25 Go to previous messageGo to next message
David VavraFriend
Messages: 1426
Registered: October 2012
Senior Member
I don't see any Problems that you've pasted.
You also have attached your post to a very old one.
Unless you are experiencing similar problems, you should start a new thread.

This issue has been mentioned before
Here's the fist link that popped up:
https://www.eclipse.org/forums/index.php/t/636348/
I found it by googling the line in your post starting with window.setTitle("Bullets on screen:

Often of the problems with Eclipse flagging code that the compiler is happy with
can be fixed by rebuilding the project index.
Re: Multiple "could not be resolved" problems [message #1834787 is a reply to message #1816408] Tue, 17 November 2020 22:09 Go to previous message
VST TOWN is currently offline VST TOWNFriend
Messages: 1
Registered: October 2020
Junior Member
Problem can be with Eclipse flagging code
Previous Topic:-std=c++17 makes things worse instead of fixing them
Next Topic:Can I use CDT to debug COFF object file?
Goto Forum:
  


Current Time: Thu Oct 10 01:46:39 GMT 2024

Powered by FUDForum. Page generated in 0.04173 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top