[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Question regarding "Create Parser Log"
|
Hi Markus,
1.
There are stille some scanner info related sections that are unclear to
me:
- Local Include Search Path (option -iquote):
- Preincluded files (option -include):
- Preincluded macro files (option -imacros):
I
guess that these sections do not contain any data that has been
somehow defined in the project properties of the respective CDT project. Am I
right?
If so
then I also assume that this data is provided through a discovery
scanner?
Greets
Marko
Hi Marko!
1. The data provided is what ends up being used by
the parser. Depending on the project configuration it is possible that it
was (partially) originated from the build-output.
2. When a file is parsed some headers that can be resolved
may already be found in the index. In this case the header is not parsed, rather
than that important information (e.g. macro defintinos) are pulled in from the
index. However, this previously indexed header may (recursively) contain other
include directives that had not been resolved at the time the header was stored
in the index. The section 'unresolved includes form headers in index'
lists those header files.
Markus.
Hello everybody,
I recently encountered this context menu which could be pretty good for
debugging and tracing indexer problems for a given file.
Unfortunately there is no help page available that describes the content
of the file. I have some questions regarding some sections of the log
file.
1. The data for the first few sections is retrieved from the scanner info
provider for the selected resource.
Does this mean that the data for these sections is
filled in with the data discovered in the log file of the executed
build?
2. Section "Unresolved includes (from headers in
index):"
Are here all unresolved includes listed or just the ones
that have been encountered when parsing the selected file?
Greets Marko
