| Re: [cdt-dev] Issues with CDT 9.8.0 / Eclipse 2019-06 |
Davin, this is a good example of one of the problems we have when we build against the latest platform. It means that old build are not as easy to reproduce. Generally speaking you can use the HEAD cdt.target file when doing your bisection, but that does not help when the problem is not just CDT.
While the underlying issue you raised here has now been resolved, please let cdt-dev list know if there is anything else we can do on this to help out.
Jonah
_______________________________________________Hi all,
I'm a user and occasional contributor to Eclipse CDT. I want to ask for help in tracking down the cause of a problem that is biting me after updating.
I've just updated to Eclipse 2019-06 and with it CDT 9.8.0 (after using 2019-03 with 9.7.2). With that update, one of my projects is suddenly showing a lot of "Symbol 'name' could not be resolved" for no clear reason and with no apparent solution; I've tried the usual tricks such as re-building the index.
From a little investigation, it appears that the errors are shown if the symbol is defined in a header file that is included only indirectly. If the symbol is defined in a header that is included directly from the source file where the symbol is referenced, everything's ok.
For example I have a line of code:
if (signame == "HUP") return SIGHUP;
The "SIGHUP" is underlined and reported as symbol-not-resolved. However, the appropriate header file (csignal) is *indirectly* included. If I add "#include <csignal>" to the top of the source file containing the line of code above, the problem does go away. Note that even when the "Symbol could not be resolved" error is displayed, going to the declaration works just fine.
Going back to a pre-CDT 9.8.0 build (which I had built myself previously) in Eclipse 2019-06, the problem goes away.
I wanted to bi-sect this issue to see if I can identify when it began. However, it seems I'm unable to build the tagged CDT 9.8.0 (using maven):
[INFO] Fetching p2.index from http://download.eclipse.org/cbi/updates/license/2.0.1.v20180423-1114/
[INFO] Adding repository http://download.eclipse.org/eclipse/updates/4.12milestones/S-4.12RC1a-201905310245
[ERROR] Failed to resolve target definition /home/davmac/eclipse-cdt/ws/cdt-git/releng/org.eclipse.cdt.target/cdt.target: Failed to load p2 metadata repository from location http://download.eclipse.org/eclipse/updates/4.12milestones/S-4.12RC1a-201905310245/: No repository found at http://download.eclipse.org/eclipse/updates/4.12milestones/S-4.12RC1a-201905310245. -> [Help 1]
So, does anyone have any clues about the problem itself, and secondly can anyone help with building non-HEAD using maven?
Thanks,
Davin
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev