Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Re: org.eclipse.cdt.make.core.ScannerConfigurationDiscoveryProfile: allowing inheritance ala superClass

On Fri, May 23, 2008 at 3:37 AM, Mike Frysinger wrote:
> 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 ...

blah, and i'm only 3 months late:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=219940
-mike


Back to the top