| AW: [cdt-dev] C source file characteristics |
|
Hi Delicia,
this may be just because the minute you explicitly add a
source folder to a managed make project, then the project folder is no more
considered a source folder. Afaik this means that at least the indexer will no
more scan the project folder for sources. Maybe it has a deeper impact on the
project so that source files simply are not recognised in the project folder
anymore.
Greetings
Norbert Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Delicia Gesendet: Mittwoch, 13. September 2006 14:55 An: cdt-dev@xxxxxxxxxxx Betreff: [cdt-dev] C source file characteristics Hi,
I have made use of the
"org.eclipse.cdt.managedbuilder.core.buildDefinitions" extension
point to create my
own toolchain.
Now, when I create a managed make C project with my
toolchain plugin, I add a
'C source file' (toplevel.c). This has the standard
'C source icon'. It also has a + sign, which
when expanded, displays contents similar to what appears in the 'Outline view'
I now add a 'C source folder' to the
project.
The minute I do this, the original characteristics
of toplevel.c change (icon changes and + sign disappears).
Note that this does not happen if I add a
'plain' folder to the project (instead of a 'Source folder').
Have I missed out on adding some functionality to
my toolchain plugin, which is causing this behaviour?
Thanks,
Delicia.
|