Skip to main content
Jump to: navigation, search

CDT/Obsolete/CoreBuildCommandLauncher

< CDT‎ | Obsolete
Revision as of 17:12, 16 October 2017 by Slewis.composent.com (Talk | contribs)

What Is The Issue?

bug513589 was introduced to support the use of docker containers for doing CDT builds. Jeff Johnston has implemented org.eclipse.cdt.docker.launcher, which depends upon linuxtools project's docker APIs for the managed builder. It does this by creating a ContainerCommandLauncher class implementing ICommandLauncher which delegates any build/clean commands to an underlying docker container. Impls of ICommandLauncher like ContainerCommandLauncher are introduced in managed builder via the ICommandLauncherFactory extension point.

Core Builder

It seems that the core builder is the future for cdt building.

ICommandLauncher and Core Builder

The core build has the concept of an IToolChain, which is an extension point that allows new tool chains to be introduced via additional plugins and existing toolchains to be reused across project types and their associated ICBuildConfiguration impls. An IToolChain is associated with a ICBuildConfiguration typically upon construction by the cbuild configuration provider. There is also a method: IToolChain getToolChain() on ICBuildConfiguration to get the associated tool chain for that core build configuration instance.

Back to the top