[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-core-dev] Extending includes resolving algorithm
|
No, you cannot extend the include file resolution. Is your builder
doing anything else other than using the correct include search path?
Markus.
The builder runs gcc with -i options to find includes. We can pass all
include pass to CDT but it works really slow. That's why I asked if can
resolve resolve includes without adding them to includes list.
Just one more questions. Let's we have the following code
Project
BlaBlaFolder
src
File1.cc
File1.hh
The File1.cc contains:
#include <File1.hh>
It won't be resolved by CDT if the folder is not added to include pathes.
But if we add the folder the File1.hh will be parsed twice. It seems CDT
handles the same *.hh file as two different files. Moreover the second
parsing will be performed on filesystem OS which is not so fast as Eclipse
workspace.
May be it is possible to avoid double parsing and working with OS filesystem
in our case?
Thanks!
--
View this message in context: http://www.nabble.com/Extending-includes-resolving-algorithm-tp23196341p23212071.html
Sent from the Eclipse CDT - core mailing list archive at Nabble.com.
