Hi Doug,
As mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=180266#c1
The discovery mechanism can be currently used in two modes:
1. "Per-resource _type_" (per-language) mode - is the mode when different profiles can be
asssociated with different resource _types_ (different tools/input types), this
allows, having different settings discovered, e.g. for C and C++ source files and for different tools used by the project.
This mode also allows to have different profile settings for different folders.
Only "project" profile types are allowed with this mode currently.
2. "Configuration-wide" mode - is the mode when only one profile (one
IScannerConfigBuilderInfo2 setting) is used for discovering scanner info for
the whole project/configuration. This is the mode simple to the one was in MBS
3.x and Standard Make 3.x
With this mode both "project" and "per-file" discovery profiles are allowed.
Both modes should be
functional for both Makefile and Managed projects as the only principal
difference between those two types of projects is that in the “Managed”
case the makefile generation is performed, while in the “Standard”
case it is not.
Mikhail
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: Wednesday, August 01, 2007
10:49 PM
To: CDT
General developers list.
Subject: [cdt-dev] Another
Question
Hey gang,
I think I’ve figured out how to get my build
output parser called during builds. I needed to set the “Discovery
profiles scope” to be Configuration-wide instead of Per Language.
Can someone explain what the difference is?
In my small understanding of the symptoms, it looks
like Makefile projects should always be Configuration-wide, since that seems
the be the only way a build output parser will run. Yes/no?
Thanks,
Doug Schaefer,
QNX Software Systems
Eclipse CDT Project
Lead, http://cdtdoug.blogspot.com