Skip to main content

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

On 2016-07-18, 4:44 PM, "cdt-dev-bounces@xxxxxxxxxxx on behalf of
c.sell@xxxxxxxxxxxxxxx" <cdt-dev-bounces@xxxxxxxxxxx on behalf of
c.sell@xxxxxxxxxxxxxxx> wrote:

>>> my "strategy" would be to support anything you can do with CMake.
>>> Otherwise, its not CMake support IMO. My ideal would be to somehow
>>> adapt the CMake object model to the eclipse-internal object model, as
>>> CLion seems to be doing it. QtCreator also handles CMake seamlessly. I
>>> wouldn't want to go through some json file that is output by CMake,
>>> but rather directly access their classes.
>>
>> That would be interesting. Though CMake is written in C++ which would
>>make
>> it pretty hard to use their classes directly. That¹s why we propose
>>using
>> the current json, with any future enhancements, as an interchange
>>format.
>> But if you think you can put something together, that would be
>>interesting.
>
>the C++/Java mismatch is not much of an issue, I'd take care of that.
>What I do not understand well is the CDT architecture / build model.
>So if you could give me some guidance where and how to integrate, I'd
>tackle this. I do understand eclipse extensions/extension
>points/schemas - it's just the CDT stuff I am not familiar with.

Best place is to look at the code for the CMake plug-ins. Then look at
everything in ICBuildConfiguration and friends. That¹s the root of the new
build model. There isn¹t much to it and it¹s all really new and barely
documented but you should be able to see how things flow. Qt qmake
projects are working if you want to see an example of it in action.

BTW, I also have in mind of creating an external plug-in that packages up
CMake and ninja to make it easier to install and distribute it from the
Eclipse Marketplace. The licenses are friendly and I may even be able to
get approval to host it at Eclipse.

Which does bring up the point that if you want to interface with the CMake
source directly, we¹ll need to get approval from Eclipse legal, even if we
don¹t ship it. But again, I¹m not sure that will be a big issue. My bigger
concern is that it may not even be necessary, but I¹ll leave that to your
analysis.

Doug.

>
>chris
>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit
>https://dev.eclipse.org/mailman/listinfo/cdt-dev



Back to the top