[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] problems with ScannerConfigurationDiscoveryProfile

I think, it would be good NOT to define my own scannerConfigDiscoveryProfileId and ScannerConfigurationDiscoveryProfile at all, just inherit it from cdt.managedbuild.tool.gnu.c.compiler and dynamically change "run -> command" from "gcc" to "lsbcc".

Andrey.

On Wed, 09 Sep 2009 16:34:47 +0400, Andrew Gvozdev <angvoz.dev@xxxxxxxxx> wrote:

Hi,You can change command and arguments in "run" element in the extension
point or in UI. Why do you need to change it dynamically? Are you talking
about command generating compiler specs?

Andrew

On Wed, Sep 9, 2009 at 6:02 AM, Andrey Tretyakov <andrromeda@xxxxxxxxx>wrote:

Hello,

I'm developing my own gcc-like toolchain (based on CDT GCC). It uses the
special compiler "lsbcc" instead of "gcc".
I know, that I also have to override scannerConfigDiscoveryProfileId
attribute and use ScannerConfigurationDiscoveryProfile extension point. I
need to use the same ScannerConfigurationDiscoveryProfile for "lsbcc", as
for "gcc", except the "command" attribute (i.e. to replace "gcc" command
with my special compiler command ("lsbcc")). So, it seems unnecessary to
implement manually all interfaces ScannerConfigurationDiscoveryProfile
points to. I also can't import into my plug-in the classes that are used
by standard GCC, because they use a lot of other internal classes.


So, the question is:
Is there a way to dynamically change "command" attribute for
ScannerConfigurationDiscoveryProfile?
If there is no, then are there public default implementations of needed
interfaces of ScannerConfigurationDiscoveryProfile?

P.S.
I use CDT 4.0.x, 5.0.x, 6.0.

Best regards,
               Andrey.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev