User forums > Help
Unable to compile ClangCompletion cbplugin
yvesdm3000:
--- Quote from: astrapi on March 23, 2016, 10:53:33 am ---I've successfully built it (Youhouu !!) I juste have to make some changes :
translationunit.h:54 assert( first.m_id == second.m_Id ); //I change the m_id in m_Id
--- End quote ---
That's fixed in a later commit.
--- Quote ---impossible to remember what I tick (like parse documentation)
--- End quote ---
I think the 'parse documentation' tab is not implemented yet. I copied some dialog items from the regular code-completion plugin that I think we'll also need in the end.
Documentation is currently always parsed. When you don't get documentation during code-completion, then this is because there is a timing issue that I'm aware of.
Don't expect the documentation to be feature-complete, it is not.
Regarding documentation, in the 'advanced'-tab there is now the option to use all comments as documentation and not only DoxyGen-type. That option should really be moved to the 'documentation' tag, but it's allready there ready for use.
The diagnostics-tab should all be implemented, and some '-W' options in the latest should also work, as is the 'advanced' tab.
Yves
stahta01:
Oops, I forgot to make an CB project change that is needed.
--- Quote from: astrapi on March 23, 2016, 10:53:33 am ---I change in linker settings wx-config --libs in wx-config --version=2.8 --libs
--- End quote ---
Tim S.
astrapi:
Cool cool cool !
I watch yours gits, and I'm ready to program !
stahta01:
I missed this post by you; I am going to answer it inline.
--- Quote from: yvesdm3000 on March 23, 2016, 10:09:31 am ---I accepted the pull request. Thanks !
It builds for me on Centos7 x64 and my own compiled wx 2.8.
Any reason why you've replaced the release and debug build with PCH and NO_PCH? I intended to use the 'Release' one with optimizations enabled and the 'Debug' one without optimizations but with debugging symbols (and assertions at a later stage). I could imagine to use pch for release and no_pch for the debug build, but the naming would then indicate a detail instead of the intention...
--- End quote ---
I did NOT realize you plan to use the 'Debug' and 'Release' targets; I can change them back if you want. I would prefer to use lower case target names when doing that.
I will work on that before doing my next pull request.
Edited named the targets 'debug' and 'release'. in the pull request I just did.
Did I do the pull request correctly?
--- Quote from: yvesdm3000 on March 23, 2016, 10:09:31 am ---I'm OK with removing the 'lib' in front since it's not needed. Initially I had problems where C::B did'nt want to accept the plugin so one starts doing every detail exactly the same as an example plugin until you find what's wrong. I don't actually know why all other plugins have 'lib' in front of them on Linux ?
Yves
--- End quote ---
I removed the lib because the zipped cbplugin file does NOT like the lib prefix; this is a bug in the CB Wizard that I might try to fix in the future.
Tim S.
yvesdm3000:
--- Quote from: stahta01 on March 24, 2016, 05:29:15 pm ---I did NOT realize you plan to use the 'Debug' and 'Release' targets; I can change them back if you want. I would prefer to use lower case target names when doing that.
I will work on that before doing my next pull request.
Edited named the targets 'debug' and 'release'. in the pull request I just did.
Did I do the pull request correctly?
--- End quote ---
Yes no problem for me
Yves
Navigation
[0] Message Index
[*] Previous page
Go to full version