[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [cdt-dev] Programmatic includes/symbols discovery
|
Title: Programmatic includes/symbols discovery
Hello Doug,
thanks for the answer.
I managed to read in the paths and symbols with the
BuilOutputReaderJob but now I am facing a strange problem. After I run the job
the discovered include paths and symbols are not visible (or not there?) in
the project properties.
When I restart eclipse and then look at the project
properties of the same project they are available!!
Do I have to refresh the project properties
somehow?
Greetings Marko
There is a build output log field in the build properties
that allow you to specify a build log file and load it. But that is in the
UI.
I don't think there is a way to programmatically launch
this. This is one of the reasons we really need to rethink how the scanner
discovery is done.
Doug Schaefer
Engineering Manager, Wind River
Systems
and Eclipse CDT Project
Lead
Hell guys,
Is there a way to programmatically invoke some code
so that CDT discovers includes and symbols from a given log file and stores
the values in the project properties so that the indexer can use these values
to work properly?
I have managed
to change the project properties programmatically so that all necessary
properties (build output file, compiler command, ...) for the discovery are
set.
If I now start the BuildOutputReaderJob it reads
the log file but the discovered elements are not stored in the project
properties.
Can anybody give me a hint?
Greetings Marko
