[cdt-dev] org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfil

["Mike Frysinger" <vapier.adi@xxxxxxxxx>]

it's pretty easy to build off of existing toolchain definitions
(especially for people who are gcc based) all due to the superClass
aspect of the buildDefinitions schema.  is there a reason the
ScannerConfigurationDiscoveryProfile schema doesnt have similar
capabilities ?  for people who merely want to take the existing gcc
scanner and change the command field from "gcc" to "whatever", it
seems like this would be ideal.  you would simply create a new
ScannerConfigurationDiscoveryProfile, create your own name/id and
declare the superClass to be like
org.eclipse.cdt.managedbuilder.core.GCCManagedMakePerProjectProfileC,
create the appropriate specsFile child and set the command to your
specific gcc commands.  all nice and clean and whenever the CDT
updates the main gcc implementation, everyone else gets the updates
for free.

as it stands, the only way a similar extensibility could be attained
is if org.eclipse.cdt.managedbuilder.internal.scannerconfig is
exported so people can copy and paste the main gcc
ScannerConfigurationDiscoveryProfile with references back to the
internal classes.

the DiscoveryProfilePage in org.eclipse.cdt.make.ui would need a
similar update so that people could inherit the default gui interface
for free as well ...
-mike