Yeah, I’m not sure what to do with clangd yet. And yes, we will work with the clangd group to figure it out.
I have an extension internally that I wrote. It bundles clangd in the extension (for all three platforms). My focus, and likely the focus of the CDT community is still on gcc and other non-clang compilers. In order for clangd to support
an operating system or processor chip, you need to add a target triple. Based on that you can add built-in macros and teach clang a bit about your target, like endianness, word size, etc. Then you can also add a Toolchain that can figure out the built-in include
path. Since clang depends on the -target option to select the triple, you also need to message the compile command in the compilation database to detect and set it. I’ll be writing an article with my experiences with QNX and ESP32 to make this work.
I’m not sure what to do with these additions. I have a fork of llvm, clang, and clang-tools-extra at the moment since you need to change all three. That’s why I need the extension, to redistribute builds to my friends and co-workers. But
I’ll see what the clangd group suggests.
But to your last point, yes, I don’t think the branding will matter if we make this really good. My main objective is to take these shared components and create an equivalent to the Microsoft cpptools extension, but open and better
☺.
Thanks! You’re bringing up great points we need to think about.
Doug.
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Marc-Andre Laperle
Sent: Tuesday, October 30, 2018 11:33 PM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Blog on the New CDT
There is already a VS Code extension for Clangd on the marketplace coming from LLVM (it’s also part of the same repo Clangd is in). Not sure about having another one with the same goals. Maybe there should be talks
about that between both communities.
About Eclipse CDT publisher name, I have mixed feelings. I have nothing scientific but personal anecdotes to back this up but…my perception over the years is that the majority of developers perceive Eclipse negatively,
at least in the non-Java community. I also don’t think people know the CDT that much. Most people know Visual Studio, Xcode and Vim but are surprised to learn that you can do C++ in Eclipse and then follows the “Why would you want to do that?”. I guess it
all depends on which circle you talk to. In the end, perhaps the name won’t be important in the long term if the technology is really good.
After the summit, Jonah and I were chatting about the VS Code extension. I was picturing the entry in the Marketplace where the publisher name was Eclipse CDT. My gut feel is that gives us a huge advantage out of
the gate. People know the CDT project and to have our name on a VS Code extension gives it instant credibility. The same will be true for Theia and any other IDE we decide to help.
For me CDT has always been a project, a group of collaborators, never a product or a thing. The product is the Eclipse IDE for C/C++. That doesn’t change. We just have other products that plug into VS Code and Theia.
But I am open to the idea of a new project at Eclipse if you can paint the picture, in particular what it would look like, and show how we’d better off.
Hi Doug,
"The idea is to bring that to other IDE front ends. And I want to remain a part of Eclipse for all the reasons
we're here in the first place. The solid foundation with strong IP providence and great IT support. I don't know a similar place to do this. That's why I believe CDT is the only place this can happen. (And, yes, I looked for one)"
These are good arguments to have these new components under the Eclipse Foundation, but IMHO not necessarily under the CDT project. It seems that a new, dedicated Eclipse Foundation project, would also have these advantages.
Funny enough, the priority is on collaborating with great people ☺. We have a lot of expertise in C/C++ development
environments. The idea is to bring that to other IDE front ends. And I want to remain a part of Eclipse for all the reasons we're here in the first place. The solid foundation with strong IP providence and great IT support. I don't know a similar place to
do this. That's why I believe CDT is the only place this can happen. (And, yes, I looked for one)
Every contributor can focus on the IDE they care about the most. The folk who left us to work on Theia can come back and help us while we help them. I can stay and continue my work with VS Code. I think we can make something very special around this and we
can be that place where all C/C++ tools integrators can converge. I think we already are.
My favorite tweet in response to mine was from Lars Vogel, "Cool. This way CDT will remain relevant and on the top edge in the future!" I think he's right.
Doug.
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx>
On Behalf Of Marc-Andre Laperle
Sent: Monday, October 29, 2018 8:19 PM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Blog on the New CDT
Hi Doug,
I just want to make sure I understand what CDT will stand for from now on. As I understand, CDT will remain the C/C++ tooling for Eclipse except that some components (language server, debug adapter) will be reusable by other IDEs (erm, editors). But would the
reference integrations/adapters with other IDEs also be hosted inside the CDT? I wonder if it would be better to have a more IDE-neutral place for this because as it stands Eclipse CDT stands for Eclipse (Classic) CDT and not for Eclipse-the-foundataion-with-other-IDEs
CDT. At least in the mind of people it is, which brings us to the marketing terms again. Can the foundation be renamed? ;) Maybe more seriously, it would be nice to see some place where all C/C++ tool integrators could converge, and I’m not sure if it can
be the (new) CDT realistically.
As for the CDT’s future as a set of Eclipse plugins, I think the strategy makes a lot of sense and is probably the only reasonable way to go. But I wonder: if the real differentiator between the Eclipse C/C++ IDE and other C/C++ IDEs is the Eclipse platform,
then how many people would go for that.
In any case, I’m hanging around if only for Eclipse nostalgia and collaborating with great people :)
Cheers,
Marc-André
> On Oct 29, 2018, at 2:45 PM, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:
>
> Hey gang, further to our discussions at EclipseCon, I've written a blog covering our strategy. Please take a look and let me know what you think.
>
> https://cdtdoug.ca/2018/10/29/eclipsecon.html
EclipseCon for me is many things. It’s a chance to meet face to face with my fellow CDT contributors. It’s an opportunity
to run things by one another that may feel awkward over the mailing list or conference calls. It’s a chance to get a good feel for what’s happening in the rest of the ...
|
>
> Cheers,
> Doug.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
|
