This question gives good answers to the question of excluding files from indexing, which are also excluded from the assembly. The question remains open: how to protect files that are part of the assembly from filling out code or code completion functions?
My use case is the TrueSTUDIO project (there was System Workbench, was naked Eclipse), which includes some modules from another project. They are wrapped in secure stubs and wrappers and should never be called directly. External modules cannot be edited because they must remain in sync with another project, so their file names and other characters conflict with the current project. When using code completion to include a header or terminate a function name, file names and module names that should not be used directly are displayed in completion lists.
I want to continue to include modules in my assemblies, but not all of their contents appear in full code / insight functions.
I see in Project Properties → C / C ++ General → Indexer there are options for setting the indexer to use a different build configuration. This is promising, but is likely to quickly lead to an indexer that is not well synchronized with the main assembly configuration.
Any tips on a practical method?
c ++ c eclipse build
Heath raftery
source share