User forums > Using Code::Blocks
Another code completion problem
MortenMacFly:
--- Quote from: eranif on August 17, 2011, 05:18:44 pm ---If you need assist, please free to email me or start a new thread about it.
--- End quote ---
Which reminds me, Eran:
We had in mind to "join forces" by trying to attach the CC codecompletion (stand-alone) library into Code::Blocks. I once tried and I have a few stubs available, but I simply don't have the time and meanwhile I'm afraid the interface to CodeLite's CC and C::B's CC has changed.
So - if anybody is willing to write a CC wrapper for Code::Blocks based on Eran's work - step forward. I think Eran did nice job concerning the separation of concerns, so it can really be seen as a stand-alone framework where we just need to match C::B's CC interface to the one of Erans.
However, as long as there is no measurement/guess about the effort our own CC has higher priority. In the end for my (and probably only my) purposes it works really well, in fact I rarely miss any information/feature.
ollydbg:
--- Quote from: MortenMacFly on August 17, 2011, 05:28:33 pm ---We had in mind to "join forces" by trying to attach the CC codecompletion (stand-alone) library into Code::Blocks. I once tried and I have a few stubs available.
--- End quote ---
There are some discussion about porting Codelite's SQLite dabase and other stuff to Codeblocks, but finally no one start doing that, because it was complex.
--- Quote from: eranif on August 17, 2011, 05:18:44 pm ---
--- Quote ---Hope it was not much work to use clang in C::B.
--- End quote ---
The basics works fine.
But when I started trying playing with it responded very slow on large files with many include files
The key was to implement the caching for clang using an automated mechanism of PCH creation by stripping the include files from a source file and generate a dummy header file which will be used as our PCH file. The generated PCH is then "injected" to the command line by the -include switch.
Another thing to put it mind is to implement a mechanism that will invalidate the cache (some entries) when needed (e.g. new header file was added to the source file)
If you need assist, please free to email me or start a new thread about it.
Eran
--- End quote ---
Thanks, you're so kind. My current work give me about one hour more or less to doing some C::B related work, so I'm not have much time to implement this right now. :D
Navigation
[0] Message Index
[*] Previous page
Go to full version