Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CMake plugins

Hi ,

I don't know exactly what you are developing for cmake.May be it is written somewhere...

However , from my viewpoint :

There are many reasons  cmake is adopted by many users. Regarding eclipse IDE . There are some good one :

* IDE independance : Users are not jailed with  an IDE, each developer may have it's preferred IDE for a lot of valuable reasons.

* It s very easy to merge and reintegrate projects settings between vcs branches :

Human readable format , easy to diff / merge (.cproject is not)

* It's very easy to add a cross compiling toolchain in minutes.

* No compatibility problems between versions.

And as well efficient.

Need for a CMake Editor ? Is there really a need ? ????? There is already one available and a  classic editor does the trick efficiently. I have seen a CMake ed plugin for eclipse exists but need not.

Problems with eclipse plugins is the compatibility .

It works at a moment, then you want to upgrade eclipse and nothing works anymore...plugins are most of the time developped by one or two persons, or a student (that's a good thing, but without a senior code review and help to improve his coding, this may be a piece of sheet's software),.

Or developed by a major company that will left the project when it will be boutght by another one, because of non interest in it ...

Because you are voluntary, you may want to have a look at the piece of code of this plugin, to make it work again.And finally , looking at it , you will understand what a chaos software is and leave it ...

That is real life of an eclipse IDE user....

So, I am very surprised to hear lot of noise around cmake here, many years after the developer's comunity adoption, like an alarm clock ringed and awaked up some people.

I switched to cmake recently with eclipse for some of these reasons. My conclusion : No need of a "an eclipse CMake plugin" , and cmake generates a nice  .cproject for you, "so, what else ?".

If there should be something done ? The logic would be enhancing cmake in eclipse project generation adding some more features and better vcs integration.



Le 15/10/2017 à 22:03, Morgner Felix a écrit :
Hi list,

I am currently working on CDT based CMake integration myself for my semester project. I plan on implementing project
creation as well as import/sync, an editor with semantic completion, and CMake server integration. I feel it would be
reasonable to join forces on this. I will be talking to my supervisor tomorrow, and wanted you to know that I would be
very much interested in contributing to the CDT CMake integration.


On Wed, 2017-06-07 at 14:43 +0000, Doug Schaefer wrote:
I think it would be good to aim at the December release for official CMake support.

Ideally we need an editor with at least syntax highlighting. Content assist would be awesome. We can either build our own editor, maybe using the new Generic Text Editor, or try and convince the CMakeEd gang to relicense and contribute. (Despite old copyright dates, it looks like it’s actively developed by a couple of people).

The other major item is to make sure users can create different build configurations. Right now everything is driven by the Launch Bar and the configuration is selected based on Launch Mode and Launch Target type. I have a start on a Build settings tab on the launch configuration which may be close to enough.

The CMake Server support would be cool too. Then I think we’d be in good shape.

I do have an itch to scratch to learn the Generic Editor but if someone has a start on one already, please let us know.

From: <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Jesper Eskilson <Jesper.Eskilson@xxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Wednesday, June 7, 2017 at 2:56 AM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] CMake plugins

I've been meaning to allocate some time to improve the CMake-plugins, but I haven't got very far. I have implemented support for the CMake server API (which is still in Gerrit), but not much else:


From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Monday, June 5, 2017 8:58 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] CMake plugins
From: <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Monday, June 5, 2017 at 2:55 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: [cdt-dev] CMake plugins

Hi devs,

Is it intentional that the CMake plug-ins are not published to Oxygen simrel repo? I know they are experimental, but it ia harder to find them not on the simrel.
Yes. They are experimental. So experimental I don’t really want the general public using them. There are still a lot of workflows that are cumbersome, hard coded, etc.

cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
cdt-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top