Enumeration of build process event trigger points
Source position: fpmkunit.pp line 528
type TNotifyEventAction = ( |
||
neaBeforeCompile, |
|
Event triggered before compilation starts |
neaAfterCompile, |
|
Event triggered after compilation completes |
neaBeforeInstall, |
|
Event triggered before installation starts |
neaAfterInstall, |
|
Event triggered after installation completes |
neaBeforeClean, |
|
Event triggered before cleanup starts |
neaAfterClean, |
|
Event triggered after cleanup completes |
neaBeforeArchive, |
|
Event triggered before archiving starts |
neaAfterArchive, |
|
Event triggered after archiving completes |
neaBeforeManifest, |
|
Event triggered before manifest creation |
neaAfterManifest, |
|
Event triggered after manifest creation |
neaBeforePkgList, |
|
Event triggered before package list creation |
neaAfterPkgList, |
|
Event triggered after package list creation |
neaBeforeUnInstall, |
|
Event triggered before uninstallation starts |
neaAfterUnInstall, |
|
Event triggered after uninstallation completes |
neaBeforeCreateBuildEngine, |
|
Event triggered before build engine creation |
neaAfterCreateBuildengine, |
|
Event triggered after build engine creation |
neaBeforeDocProject, |
|
Event triggered before documentation project processing |
neaAfterDocProject |
|
Event triggered after documentation project processing |
); |
TNotifyEventAction defines the different stages in the build process where notification events can be triggered.
This enumeration enables attaching custom actions or handlers to specific points in the build pipeline.
Build systems use these action points to execute custom commands, perform validation, or provide progress feedback.