Well, the closing session is about to start and the vendors are packing up their displays. Another successful Eclipse Summit Europe is about to go off into the sunset. For me, it was proof again why I love coming to this show. The CDT community in Europe is strong and a lot of them are doing and want to do interesting things with the CDT.
The talk I gave was on the code analysis capabilities of the CDT introducing the things you can do with the CDT's parsers and indexing framework. I also introduced the new refactoring engine that we have which really opens up a lot of cool automations you can do to analyze and refactor your code. The best part is that I had a few guys come up to me after to ask about certain analysis things they wanted to do. I'm glad I gave that talk and I hope more people take a look at what the CDT has to offer in this area.
I also had a number of people ask about the CDT managed build system. This is an area in a bit of trouble right now with the CDT. One of the key developers has left and we're struggling understanding the code that he left behind. Hopefully these vendors who have concerns about the build system will join us and get us rolling again. The CDT build model can do some pretty cool things and I look forward to seeing the different build integrations people are thinking of working.
I had a discussion with someone interested in working on the Windows debug integration I have on my wish list. I've given it a couple of tries and there is a start of one in the Target Communication Framework (TCF) agent. Hopefully we can finally get this together and have full support for the Visual C++ compiler with the CDT.
Speaking of TCF, there was a lot of interest in it from various embedded system vendors. It's a really good technology for building target agents with a clean communication protocol back to Eclipse and a services oriented architecture. I've been interested in component models for C/C++ applications and I can see how this agent could use something like that. I'll have to give it some thought and see if others are interested in getting involved in that.
It's been a fun and interesting week. Hopefully I talked to everyone who wanted to talk CDT with me. And hopefully we can get some momentum off of that to continue the growth of the CDT community. Those late nights in the hotel bar with the Eclipse gang was part of that community building and I'm going to sleep well on the flight home but it was worth it.
Hi Doug!
ReplyDeleteMy name is Ivan Muzzolini and work for Electrolux. Where can I find some documentation about the code analysis capabilities of the CDT?
Thanks!
Bye
Ivan
Wondering the same thing as Ivan :-). I've specifically been looking for good integration with some static code analysis tool such as splint or pc-lint by Gimpel? Or is there some other way of achieving the same thing?
ReplyDeleteDoug,
ReplyDeleteI would be very interested to know more about integration of Visual C++ compiler with the CDT. How could I get involved?
Thanks,
Stephen
I'm getting very close to abandoning the Visual C++ integration. It's way too much work for any individual.
ReplyDeleteAnd we have done a very poor job at documenting the extension capabilities of the CDT. If you guys would like to help, that's where you would need to start.
Doug,
ReplyDeleteRegarding Visual C++ integration, could you tell us more about the current status and the major roadblocks? What code works, and what doesn't? Is it a matter of putting in the sweat, or are there still feasibility concerns?
Our core interest is integrating dgbeng.dll with CDT debug. We can probably put in full time engineers if we decide to go ahead. How much work do you there is to a functioning state?
There is a build integration. But consider debug nowhere. Feel free to start from scratch.
ReplyDeleteok ;-) This is going to be fun.
ReplyDeleteAre there any design docs/feasibility docs for CDT/VC++ debug integration you could point us to? Do you reckon CDI being the "right" API to integrate with? I heard there is a new debug API coming up in next version of CDT - should we use that instead of CDI?
Thanks.
CDI is unofficially deprecated. DSF (Debug Services Framework) is moving from the Device Debug project to the CDT project proper over the next few weeks. I'd recommend you start there.
ReplyDeleteThe Windows debugger integration was never an official program, so there are no docs for it. I tried a number of scenarios but failed at them all. But then I never had the time to properly dedicate to it.