Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Archive/cdt-core/designs/CommandLauncher"
(Initial save) |
(No difference)
|
Revision as of 16:18, 23 June 2009
Contents
Introduction
The org.eclipse.cdt.core.CommandLauncher
extension-point was added post-CDT6 (CDT6.1 / CDT7). The functionality was proposed and implemented in bug 279818
Motivation
Many places in CDT need to run external tools. cdt.core provides a mechanism for contributing such CommandLauncher
s and UI is provided for allowing users to configure CommandLaunchers.
CDT.core provides API for discovering and creating CommandLaunchers for an appropriate type of process.
Terminology
-
processType
A type of process we wish to launch e.g. Run-Launch, Debug-Launch, Build. Seeorg.eclipse.cdt.core.CommandLauncherFactory
for supported processTypes.
-
CommandLauncher
A class extending org.eclipse.cdt.core.CommandLauncher. Provides an #execute(...) method which returnsjava.lang.Process
for a given execution.
-
CommandLauncherDialog
A contributed dialog which allows configuring advanced preferences on the CommandLauncher
-
CommandLauncherFactory
A factory for creating CommandLaunchers based on the process type currently being launched. Uses user preferences for selecting the appropriate CommandLauncher, and provides utility methods for getting and setting Advanced preferences on the launcher.
Integrating
Extension Points
org.eclipse.cdt.core.CommandLauncher
The CommandLauncher extension point allows contribution a class which extends org.eclipse.cdt.core.CommandLauncher
. See org.eclipse.cdt.internal.core.WrappedCommandLauncer
org.eclipse.cdt.ui.CommandLauncherDialog
This extension point