| RE: [cdt-dev] Need help in the maze of buildDefinitions extension point |
|
Hi Sergey, I guess what you should
do is define a new tool-chain with no super-class and add/define all the necessary
tools to it. These could be either new tools or tools having any of the “org.eclipse.cdt.build.core.*”
as a super-class. Once you do that you
could define a new project type that would use your tool-chain. In case this does not
work please create a bugzilla request providing a sample that does not work as
expected. Thanks, Mikhail From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin I'm trying to define a project type that is a slight variation of
Makefile project with "Other Toolchain". I need to change default
builder settings and discovery options. Unfortunately,
org.eclipse.cdt.build.makefile.projectType cannot be subclassed since it is not
defined anywhere in plugin.xml. I also tried to subclass
cdt.managedbuild.toolchain.gnu.base toolchain, but I was not able to hide the
tools inherited from it. unusedChildren attribute of toolChain seems to have no
effect. When I define a tool by subclassing
cdt.managedbuild.tool.gnu.cpp.compiler, I'm getting GCC C++ Compiler listed
twice in various places in the project properties UI. Is there a way to hide
tools inherited from the superslass toolchain? Am I on a grossly wrong path and
should be doing something completely different? |