Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Cmake support

Hi Martin
I am jantje the author of Sloeber (arduino eclipse plugin based on CDT available on github ;-) ) and I feel like tackling the CDT managed build system problem. I mean: Sloeber is build upon the gnuMakefileBuilder and I have ideas on how I think it should be done. But he, that is just me. So I'm looking for as mutch input as I can and I was wondering how you tackled this yourself. Can you point me to some documentation or explain how you did it and most importantly: how you think it should be done?

Best regards


PS I agree on your point 4

Op 22/01/2020 om 22:39 schreef 15 knots:
Hi Jonah,

Am Mi., 22. Jan. 2020 um 17:11 Uhr schrieb Jonah Graham

In the past you have expressed a willingness to contribute cmake4eclipse to the CDT project?
IIRC, I was willing to place the Editor *cmakeed* under the Eclipse
foundation with its own update site, but not as a *CDT* project. The
fortran guys might want the editor too, as well as people who want to
integrate/install it in a CDT-derived IDE (e.g. Nvidia Insight).

Are you still willing to consider that - and join the Eclipse CDT project as a committer to help with ongoing maintenance? What I would expect is that we deprecate & remove the existing cmake implementation in Eclipse CDT and include only the one you developed starting in CDT 10. That would mean that cmake4eclipse is shipped to all CDT users via the Eclipse IDE for C/C++ Developers package on
cmake4eclipse is for managed buld. AFAIK from this list, managed buld
is going to be phased out. I do not hink it is worth the effort of
moving it to eclipse foundation.

I see the need for users to have good cmake support easily installed
until core build is mature, but actiually I do not want to maintain it
as a CDT maintainer. Reasons are:

1) I do not do much C devlopment any longer. If it were under the CDT
umbrella, I fear I will loose interest in maintaining it over time.
Having the source on github and the artifacts on bintray, I can enjoy
user feedback and download stats [1] and stay exited.
2) It is easier for users to file issues on github since most of them
already have an account on github. If the plugin is a CDT project,
user will have to create an account on CDT to file issues. And it
might be more likely that issues of the plugin get ignored on the CDT
bug tracker.
3) cmake4eclipse is already well-known (google for it) and even some
open source projects mention it in their 'build with Eclipse' FAQs.
4) Sorry for the rant here: To develop the plugin, I had to deeply
dive into the CDT code base. What a mess: Almost no code
documentation, documentation that lies, no real developer FAQ and lot
of unsued code. Sorry, I do want want to see my properly documented
code among that mess.

If the CDT team want good cmake support for CDT managed build,
wouldn't it be possible to add one of the cmake4eclipse download repos
on bintray [2] to the CDT product? These are build from pristine
sources on Or just mirror the github repo inside
Eclipse foundation and build & publish it there?


[1] 5022721 downloads
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top