From 553cfcce4259cb2a0d622110ad52811d9ab357b6 Mon Sep 17 00:00:00 2001 From: Björn Persson Date: Sun, 23 Feb 2014 15:28:49 +0100 Subject: multi-step installation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit · Added pre- and post-installation hooks to the installation phase. · No attempt to install staged files is made if the build doesn't stage any files. --- manual.en.html | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'manual.en.html') diff --git a/manual.en.html b/manual.en.html index 4d1c780..17f213a 100755 --- a/manual.en.html +++ b/manual.en.html @@ -594,6 +594,29 @@ be added as prerequisites.

This preprocesses files that need to be preprocessed before projects are built.

+
postinstall
+

You may add a recipe to postinstall if there are commands +that need to be run on the target system after the files have been installed. +This will typically be commands that modify existing files on the target +system. Normally “make install” runs postinstall after +installing the files when DESTDIR is empty, but skips it when a +directory is specified in DESTDIR, because such commands need to be +run on the target system, not on a build server. Installing users can override +this default behaviour by setting do_postinstall to +“true” or “false”.

+ +
preinstall
+

This is like postinstall except that it's run before the +files are installed, not after. Installing users can control it with +do_preinstall.

+ +
install_files
+

You may add a recipe to install_files if any files have to be +written, deleted or moved after the staged directory tree has been copied. +Avoid using this if possible. It's better to stage all the files correctly +under the staging directory in the build phase, but this hook exists if you +really need it for some workaround.

+
configure

“make configure” is used to set values in the persistent configuration and to set up a -- cgit v1.2.3