You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have used Eclipse with CDT on Linux for 15 years developing Mixxx and enjoyed it a lot, it had an outstanding Indexer at those days and well integrates into my workflow.
In between I tried Qt Creator, KDevelop and even VSCode. But I always came back mainly because the nice call hierarchy view. We have maintained a nice guide how to set everything up for new contributors
here https://github.com/mixxxdj/mixxx/wiki/Eclipse
Mixxx had hundreds of contributors since.
However Mixxx was growing and Eclipse CDT probably not. The indexer becomes slow and unreliable the RAM requirement was enormous. Finally the Indexer became useless, Eclipse often stalled during indexing. Now I can't use it anymore, because it crashes in addition as soon the "compile_commands.json" is read.
I moved to VSCodium recently and was impressed how snappy everything works, using the clangd indexer and CMake Tools.
Now I am a bit torn what to do. Shall we take down our Eclipse guide and recommend not to used Eclipse ?
Is Mixxx really to big for using it effectively with Eclipse CDT, or do we something essentially wrong?
If you have interest to keep Eclipse CDT as an option to develop Mixxx, we need help.
Can one with CDT insight knowledge review our guide at https://github.com/mixxxdj/mixxx/wiki/Eclipse?
What went wrong? Maybe you can also Test Eclipse CDT using Mixxx, I am happy to work with you to make Eclipse a reasonable choice again.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I have used Eclipse with CDT on Linux for 15 years developing Mixxx and enjoyed it a lot, it had an outstanding Indexer at those days and well integrates into my workflow.
In between I tried Qt Creator, KDevelop and even VSCode. But I always came back mainly because the nice call hierarchy view. We have maintained a nice guide how to set everything up for new contributors
here https://github.com/mixxxdj/mixxx/wiki/Eclipse
Mixxx had hundreds of contributors since.
However Mixxx was growing and Eclipse CDT probably not. The indexer becomes slow and unreliable the RAM requirement was enormous. Finally the Indexer became useless, Eclipse often stalled during indexing. Now I can't use it anymore, because it crashes in addition as soon the "compile_commands.json" is read.
I moved to VSCodium recently and was impressed how snappy everything works, using the clangd indexer and CMake Tools.
Now I am a bit torn what to do. Shall we take down our Eclipse guide and recommend not to used Eclipse ?
Is Mixxx really to big for using it effectively with Eclipse CDT, or do we something essentially wrong?
If you have interest to keep Eclipse CDT as an option to develop Mixxx, we need help.
Can one with CDT insight knowledge review our guide at https://github.com/mixxxdj/mixxx/wiki/Eclipse?
What went wrong? Maybe you can also Test Eclipse CDT using Mixxx, I am happy to work with you to make Eclipse a reasonable choice again.
All reactions