| RE: [cdt-dev] A few more build/project questions |
|
Hi Sascha, Please see my comments embedded below. Mikhail -----Original Message----- 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. [Mikhail] The “Environment” tab represents the environment
settings to be used for the Build process. The “CDT Variables” is
the same as the “Build Macros” functionality present in MBS 3.x,
i.e. the build macros/variables can be used in option values, path/symbol
values as ${variable_name}. The variable reference gets resolved when the given
value is used, e.g. variables used in the option values get resolved while
makefile generation, etc. The reason you are seeing the “Path” and other environment
variables in the Build Macros/variables settings is because all environment
variables can be used as build macros/variables in CDT settings and are treated
as build macros/variables. - 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. [Mikhail] There has been quite a long discussion regarding this in the
Project Model bugzilla sometime ago. Please refer to the https://bugs.eclipse.org/bugs/show_bug.cgi?id=115935
for detail 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? [Mikhail] No, as
far as I can tell :( 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 ? [Mikhail] Try
implementing the custom dependency calculator as mentioned above and let me
know if you have any problems with this approach. 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 _______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev |