Class
IdePipelineStageLauncher
Constructors
ide_pipeline_stage_launcher_new
Creates a new IdePipelineStageLauncher
that can be attached to an
IdePipeline
.
Available since: 3.32
Instance methods
ide_pipeline_stage_launcher_get_ignore_exit_status
Gets the “ignore-exit-status” property.
Available since: 3.32
ide_pipeline_stage_launcher_get_use_pty
ide_pipeline_stage_launcher_set_clean_launcher
ide_pipeline_stage_launcher_set_ignore_exit_status
Sets the “ignore-exit-status” property.
Available since: 3.32
ide_pipeline_stage_launcher_set_launcher
ide_pipeline_stage_launcher_set_use_pty
If use_pty
is set to TRUE
, a Pty will be attached to the process.
Available since: 3.32
Methods inherited from IdePipelineStage (25)
Please see IdePipelineStage for a full list of methods.
Properties
Ide.PipelineStageLauncher:clean-launcher
Ide.PipelineStageLauncher:ignore-exit-status
Ide.PipelineStageLauncher:launcher
Ide.PipelineStageLauncher:use-pty
Properties inherited from IdePipelineStage (7)
Ide.PipelineStage:active
This property is set to TRUE
when the build stage is actively
running or cleaning.
Available since: 3.32
Ide.PipelineStage:check-stdout
Most build systems will preserve stderr for the processes they call, such
as gcc, clang, and others. However, if your build system redirects all
output to stdout, you may need to set this property to TRUE
to ensure
that Builder will extract errors from stdout.
Available since: 3.32
Ide.PipelineStage:completed
The “completed” property is set to TRUE
after the pipeline has
completed processing the stage. When the pipeline invalidates
phases, completed may be reset to FALSE
.
Available since: 3.32
Ide.PipelineStage:disabled
If the build stage is disabled. This allows you to have a stage that is attached but will not be activated during execution.
Available since: 3.32
Ide.PipelineStage:name
The name of the build stage. This is only used by UI to view the build pipeline.
Available since: 3.32
Ide.PipelineStage:stdout-path
The “stdout-path” property allows a build stage to redirect its log messages to a stdout file. Instead of passing stdout along to the build pipeline, they will be redirected to this file.
Available since: 3.32
Ide.PipelineStage:transient
If the build stage is transient.
Available since: 3.32
Properties inherited from IdeObject (2)
Ide.Object:cancellable
The “cancellable” property is a GCancellable
that can be used by operations
that will be cancelled when the IdeObject::destroy
signal is emitted on self
.
Available since: 3.32
Ide.Object:parent
The parent IdeObject
, if any.
Available since: 3.32
Signals
Signals inherited from IdePipelineStage (3)
Ide.PipelineStage::chain
Ide.PipelineStage::query
The IdePipelineStage::query
signal is emitted to request that the
build stage update its completed stage from any external resources.
Available since: 3.32
Ide.PipelineStage::reap
This signal is emitted when a request to rebuild the project has occurred. This allows build stages to ensure that certain files are removed from the system. For example, an autotools build stage might request that “configure” is removed so that autogen.sh will be Executed as part of the next build.
Available since: 3.32
Signals inherited from IdeObject (1)
Ide.Object::destroy
The “destroy” signal is emitted when the object should destroy itself and cleanup any state that is no longer necessary. This happens when the object has been removed from the because it was requested to be destroyed, or because a parent object is being destroyed.
Available since: 3.32
Signals inherited from GObject (1)
GObject.Object::notify
The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.