Thread: [CEDET-devel] ede-compdb status
Brought to you by:
zappo
From: Alastair R. <ala...@gi...> - 2015-01-08 03:21:41
|
Hi David, Thanks for reaching out - a few months ago I moved to a new state and new job and completely missed the fact that my domain email stopped working. Fixed now. In fact I didn’t realise anyone else was using ede-compdb, even though i think it has general utility, particularly for C and C++ programmers. Anyway I’m still actively maintaining it, having made a few tweaks on it as a result of my new job, which had a new build system etc. Anyway, glad there is still some interest. > Were there some open issues with the code? I think all that was still > needed was to include the documentation from your Readme.org into our > Texinfo manuals. However, if you don't feel comfortable around Texinfo, > we can convert it, though. Off the top of my head I think the outstanding work is: - Integrating the main compdb code - most of this work is independent of the rest of EDE, but there is a bit of overlap with compiler flag detection. - Unit tests. These may be problematic; I’ve been using some third party libraries imported through cask. I don’t know if this is feasible within cedet proper. - Converting documentation into Texinfo (as you say) - Check for updates required as a result of changes to EDE - particularly the recent Locate Dominating File merge. Actually this is something I need to do regardless. > Lately, I also had an idea: wouldn't it be cool if the compilation > database could be generated from a compilation buffer? I mean, I use gcc > and I could use this 'bear' utility to generate the db, but I run 'make' > inside Emacs anyway, so all the data that is needed is right there in > the output. Eclipse has the same feature for 'make'-based projects: it > scans the output for preprocessor symbols, includes, etc. It's very > useful. Yeah that sounds possible, certainly. Presumably it would persist this information somehow? Perhaps write out a compilation database file? It’s an interesting idea. |
From: David E. <de...@ra...> - 2015-01-10 15:17:36
|
Alastair Rankine writes: > Off the top of my head I think the outstanding work is: > > - Integrating the main compdb code - most of this work is independent > of the rest of EDE, but there is a bit of overlap with compiler flag > detection. > > - Unit tests. These may be problematic; I’ve been using some third > party libraries imported through cask. I don’t know if this is > feasible within cedet proper. > > - Converting documentation into Texinfo (as you say) > > - Check for updates required as a result of changes to EDE - > particularly the recent Locate Dominating File merge. Actually this is > something I need to do regardless. Do you need help with this? Otherwise, you now have push rights to the Git repository, so feel free to just check it in (I'm not sure if you followed this list; CEDET switched to Git, the repository is now at "ssh://use...@gi.../p/cedet/git"; you can also use https if you prefer). > Lately, I also had an idea: wouldn't it be cool if the compilation > database could be generated from a compilation buffer? I mean, I use gcc > and I could use this 'bear' utility to generate the db, but I run 'make' > inside Emacs anyway, so all the data that is needed is right there in > the output. Eclipse has the same feature for 'make'-based projects: it > scans the output for preprocessor symbols, includes, etc. It's very > useful. > > Yeah that sounds possible, certainly. Presumably it would persist this > information somehow? Perhaps write out a compilation database file? > It’s an interesting idea. Yes, I think the first step would be to have code that creates a JSON compilation database file from a compilation buffer. We can first put this into CEDET, but I think in the long run we should try to get this into compile.el in Emacs proper. If we had this, we could simply tell EDE "Here's a compilation buffer, please generate a project from that", and it would simply call the function that creates the compilation database and then ede-compdb reads it in. -David |