User forums > Help
When will Code::Blocks support "noexcept" specifier?
Alpha:
During runtime, the clang plugin has two main requirements: access to the libclang binary (.so or .dll) and that the system has standard library headers written in valid (according to Clang's standards) C++. I recall reading somewhere that Clang can parse the vast majority of MSVC headers (although, this plugin is not yet set up to look for them). On my computer, it has worked fine using the headers bundled with GCC/MinGW.
The rest of Clang/LLVM is only necessary if a prebuilt libclang is unavailable for the system.
--- Quote from: EnterTheNameHere on January 20, 2014, 01:40:01 pm ---[...] so why not use Parser used by compiler?
If it would work like this, then it's fantastic.
--- End quote ---
Clang powered CC:
oBFusCATed:
Can you link to libclang statically?
Otherwise it looks promising.
One question:
Do CC still works for random headers in the source tree, but not in the project?
I love this hidden feature of the current CC plugin. At work we have tons of code
and not all of it is kept in cbp project, so completing random headers or cpps would be great if could be kept.
Alpha:
--- Quote from: oBFusCATed on January 21, 2014, 12:45:12 am ---Can you link to libclang statically?
--- End quote ---
The precompiled binaries I downloaded only contain shared libs; I will have to look into seeing if the build system supports static libraries.
--- Quote from: oBFusCATed on January 21, 2014, 12:45:12 am ---Do CC still works for random headers in the source tree, but not in the project?
I love this hidden feature of the current CC plugin. At work we have tons of code
and not all of it is kept in cbp project, so completing random headers or cpps would be great if could be kept.
--- End quote ---
From my testing, it works approximately as well as the current CC plugin with unbound files. (This largely depends on how well it is able to find the referenced header files, which seems to be the same as the current CC plugin.)
Yamakuzure:
First: I now see where this really is beneficial using clang.
And for a bit of on topic: Thank you, MortenMacFly
--- Quote from: oBFusCATed on January 20, 2014, 09:01:03 pm ---
--- Quote from: Yamakuzure on January 20, 2014, 10:47:10 am ---So for 1K lines for code completion, one has to install (and on source based distributions like Gentoo Linux compile) the full LLVM and CLANG suites? Sweet.
--- End quote ---
On the source based distros you get llvm/clang compiled for you automagically, at least if you're using some smart source based distro.
And by the way the chance that you won't have llvm/clang installed in the future is getting smaller and smaller.
--- End quote ---
Yes, unless you have an intel graphics chipset. In that case there is no point to use mesa with LLVM as there is no Gallium3D support for modern intel HD. And apart from mesa there aren't many consumers for LLVM, yet.
Currently, on Gentoo at least, there are:[*]dev-lang/ghc : The Glasgow Haskell Compiler
[*]dev-lang/rubinius : A re-implementation of the Ruby VM designed for speed
[*]media-libs/mesa : OpenGL-like graphic library for Linux
[*]sys-devel/sparse : C semantic parser
[*]app-vim/youcompleteme : vim plugin: a code-completion engine for Vim
[/list]That is not much. And I doubt this list is more excessive elsewhere.
However, there is the next part:
--- Quote from: Alpha on January 21, 2014, 01:19:13 am ---
--- Quote from: oBFusCATed on January 21, 2014, 12:45:12 am ---Can you link to libclang statically?
--- End quote ---
The precompiled binaries I downloaded only contain shared libs; I will have to look into seeing if the build system supports static libraries.
--- End quote ---
Well, the main llvm configure script understands these options:
--- Code: --- --enable-shared Build a shared library and link tools against it
(default is NO)
--enable-embed-stdcxx Build a shared library with embedded libstdc++ for
Win32 DLL (default is NO)
--- End code ---
So as far as I understand it, static linking is the default. Although the second option more sounds like whether or not to statically link libstdc++ into the windows dll, so no static library here (it seems).
Navigation
[0] Message Index
[*] Previous page
Go to full version