Hi,
I did a bit of comparison between the various possibilities:
* managed build + compile commands database parser
** the most flexible approach, works with any build system that can generate compile_commands.json
** the generation step is manual, creating different configurations require a bit of work, probably one would script it
** was not immediately clear that I had to enable the GCC built-in parser too, after that system symbols were indexed properly
* cmake4eclipse
** probably the best solution if using cmake, the generation step is integrated in the build, easy to create multiple configurations
** needs an additional plug-in
* core build cmake
** uses the compile commands file to feed the indexer, set-up is very simple
** suffers from the limitations of core build, e.g. complete lack of build configurations (at least there is no UI), not really usable beyond an hello-world project
Martin, I see your plug-in provides two additional parsers, one being for the built-ins, what is the difference with the GCC built-ins?
does it take into consideration the toolchain defined in cmake?
cheers
Fabrizio
