[cdt-dev] A few more build/project questions

["Sascha Radike" <sradike@xxxxxxxxxxxx>]

Hi,

I know everyone is busy due to upcoming feature freeze. But working on a
product based on CDT 4.0 I can't resist to ask a few more questions ;) .

- Build options: Is there a way to dynamically provide option values? Right
now I've implemented an IoptionApplicability calculator. Since the
calculator gets called before any command line generation I use this
interface to update option values if required. This works well in most
cases, but not always because the caller of the calculator has a copy of the
old value.
So...is there a recommended way for providing dynamic option values or at
least changing values right before CDT needs them for command line
generation ?

- What exactly is the difference between C/C++ Build -> Environment
(variables) and C/C+ Build -> Variables ? I can set and edit PATH on both
pages.

- How do the eclipse "Project References" and the CDT C/C++ General / Path &
symbols / References work together? Right now I don't see any connection  -
which is confusing.


The next two items are bugs which I mentioned before...and I know everyone's
busy. But they are critical to our project, so I would be thankful for a
reply:

- The internal builder: We would love to use this new feature! Right now the
internal builder is not reliable due to the indexer based dependency
calculations and the build configurations issue - See bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=172919#c36 . A solution would
be a dependency calculator based on GNU GCC dependency files. Mikhail wrote:
"This is implemented basically ;), i.e. in case the tool specifies the
IManagedDependencyGeneratorType.TYPE_CUSTOM dep calculator it should be used
instead of the PDOM Dependency calculator."

My questions is: Is such a calculator planned for 4.0? If not so... is it
possible to at least to provide the necessary interfaces and/or extensions
so we could try to setup our own gcc calculator ? We really don't want to
drop the internal builder. :-\

- Our plugins provide source locations based on external settings. Thanks to
Mikhail for the great external settings provider interface! Those source
locations can also be folders which are not children of the project root. So
the following project layout will be quite common:

Project
  folderA [Excluded]
    folderB [...]
       folderC [Included]   <-- Source location

Unfortunately this shows up as

Project
  folderA/folderB/folderC
  folderA
    folderB
   
...which not only looks confusing but also messes up our project explorer
extensions. See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=181020.

My question: What are the plans regarding this issue? I'd like to avoid any
hacking because I just don't know enough about the internals of the C Model.


Thanks in advance

Sascha