[cdt-dev] adding tools to *existing* toolchains?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] adding tools to *existing* toolchains?

From: "Andras Varga" <andras@xxxxxxxxxxx>
Date: Wed, 12 Dec 2007 13:32:13 +0100
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: Acg8RzwtmM8eNMlnQ9+hCwQFE45iNgAcpb2A

Hi all,

Why can't I contribute tools, macro resolvers etc to EXISTING toolchains?
Would be much better than "subclassing" each and every existing toolchain!

In the Eclipse platform, I don't have to subclass from Perspective, View etc
definitions in plugin.xml to be able to contribute things (actions etc) to
them!

See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=212127

Regards,
Andras

Follow-Ups:
- Re: [cdt-dev] adding tools to *existing* toolchains?
  - From: Wieant Nielander

References:
- [cdt-dev] What happened to failed build notification from the file name in the tab?
  - From: Fedja Jeleskovic

Prev by Date: [cdt-dev] What happened to failed build notification from the file name in the tab?
Next by Date: RE: [cdt-dev] "assert" in cdt source vs. java compiler versionsinprojects
Previous by thread: [cdt-dev] What happened to failed build notification from the file name in the tab?
Next by thread: Re: [cdt-dev] adding tools to *existing* toolchains?
Index(es):
- Date
- Thread

Breadcrumbs