Eclipse Community Forums: C / C++ IDE (CDT) » Eclipse's Uselessness for Large C++ Projects

Home » Language IDEs » C / C++ IDE (CDT) » Eclipse's Uselessness for Large C++ Projects(Eclipse's Uselessness for Large C++ Projects)

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse's Uselessness for Large C++ Projects [message #1849556]

Tue, 25 January 2022 07:13

Kevin Nguyen

Messages: 3
Registered: January 2022

Junior Member

Hello,

After a lengthy and complicated account registration process, here I am.

For a simple application, the hello world app, Eclipse is very useful :D

index.php/fa/41577/0/

Now, we try a large C++ project, that is the KiCAD.

git clone https://gitlab(.)com/kicad/code/kicad.git

Import KiCAD as a Makefile project.

index.php/fa/41578/0/

Indexer C/C++ starting a process.

index.php/fa/41580/0/

Eclipse CDT cannot be resolved the source code and header files.

index.php/fa/41581/0/

I use Ubuntu 20.04 with all dependencies library for success compile KiCAD.

To build a CMake project like Kicad, we need to use a script bash with params.

Eclipse's Uselessness for large C++ projects as KiCAD, FreeCAD, Blender.

It cannot build, index, browse the source code...

To the developer team, please use some large projects to test CDT.

Thanks.

Attachment: p1.png
(Size: 125.29KB, Downloaded 463 times)
Attachment: p2.png
(Size: 120.19KB, Downloaded 465 times)
Attachment: p3.png
(Size: 129.27KB, Downloaded 423 times)
Attachment: p4.png
(Size: 118.84KB, Downloaded 453 times)
Attachment: p5.png
(Size: 290.23KB, Downloaded 418 times)

Report message to a moderator

Re: Eclipse's Uselessness for Large C++ Projects [message #1849565 is a reply to message #1849556]

Tue, 25 January 2022 16:22

David Vavra

Messages: 1426
Registered: October 2012

Senior Member

Quote:

Eclipse's Uselessness for large C++ projects as KiCAD, FreeCAD, Blender.

Useless? Hard to see what is essentially an editor would be useless.
I suspect you want it to do more than originally designed.
You could be more helpful by being more specific.

Did you actually import a project or did you create a new one?
Hard to tell.

Using cmake means you are pretty much on your own.
I use Make. Not that it's much different than cmake but
Importation of a make project provides additional menu options
for the indexer.

In any case, project builds are done with external systems and not CDT
Eclipse has almost no control over them.

I've used CDT with projects approaching 1e6 lines without problems.
Many third party libraries seem to be written in a way that confuse the indexer.
Nothing can be done about that.
Understand that the indexer is meant for quick cataloging.
An aide. It's not a compiler.

Report message to a moderator

Re: Eclipse's Uselessness for Large C++ Projects [message #1849573 is a reply to message #1849565]

Wed, 26 January 2022 03:30

Kevin Nguyen

Messages: 3
Registered: January 2022

Junior Member

Sorry for using the word "useless", but I wanted to get everyone's attention. There have been too many problems related to "unresolved inclusion".
I no need to compile in CDT, I need to index the source code, but CDT cannot solve libraries in the "/usr/local/include/**".
You can above image for ~5000 unresolved items and you cannot use it.
To compile a project using Cmake, I write a bash script and compile KiCAD, FreeCAD, Blender success.
I hope we will have an updated version and developers will refresh the indexer. It really has problems.

[Updated on: Wed, 26 January 2022 03:40]

Report message to a moderator

Re: Eclipse's Uselessness for Large C++ Projects [message #1849576 is a reply to message #1849573]

Wed, 26 January 2022 07:16

Joost Kraaijeveld

Messages: 273
Registered: July 2009

Senior Member

If using Makefiles to compile programs Eclipse (i.e. its indexer with auto-complete feature, code browsing etc) does not use auto-discovery features for #includes and #defines. This must be configured manually.
This must be done in the "Paths and Symbols" part of the project settings: "Project->properties->C/C++ General->Paths and Symbols" on the tabs "includes" and "symbols".

From you screens I guess the unresolved stuff is from wxWindows. Use "wx-config --cppflags" for the relevant wxWidgets values.

Use "Window->Show view->Other->C/C++ index" to find any other unresolved header files or unresolved other C/C++ symbols and add them to the project settings mentioned above.

Cheers,

Joost

Report message to a moderator