summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorkonablend <[email protected]>2009-03-05 06:57:31 +0000
committerkonablend <[email protected]>2009-03-05 06:57:31 +0000
commitd9cbd469c2cda62f205599173910ec627031dadd (patch)
tree188532861f51a1650a643e426501c2dc257fd536 /doc
parent66672c6931393a17a4ffc48c1509205d23518221 (diff)
BuildSystem:
- increased inter-contrib module rebuild sanity; ie: if an svn update is done and a new x264 tarball is available, the system will fetch it and proceed to extract->patch->configure->build->install and because it is utterly dangerous (undefined results can easily occur) to re-extract over an existing extract, the appropriate steps are taken to first rm -fr the tarball extraction directory. This is generally good practice but I'm explaining it here in detail in case some developers are taking risks like editing files in the build/ tree and erroneously assuming they will not be overwritten by either this new build system or contrib (foreign) build systems. - added contrib touch/untouch targets; see doc. - updated docs accordingly. - fixed typo for GCCargs.g.max which caused --debug=max to not operate properly. - unofficial builds will no longer rebrand naming to 'NoNameBrand' git-svn-id: svn://svn.handbrake.fr/HandBrake/trunk@2223 b64f7644-9d1e-0410-96f1-a4d463321fa5
Diffstat (limited to 'doc')
-rw-r--r--doc/texi/building/chapter.via.terminal.texi18
1 files changed, 17 insertions, 1 deletions
diff --git a/doc/texi/building/chapter.via.terminal.texi b/doc/texi/building/chapter.via.terminal.texi
index 0c323ab8c..29014819e 100644
--- a/doc/texi/building/chapter.via.terminal.texi
+++ b/doc/texi/building/chapter.via.terminal.texi
@@ -171,9 +171,25 @@ This usually invokes autotool clean.
Extra clean module; first invokes uninstall then recursively removes the module build directory.
@end table
+@anchor{terminal.targets.contrib.touch}
+@subsection Contrib Touch and Untouch
+Also available are some very granular targets which help force builds from specific cycle points. The following targets are available to touch and untouch the respective module target; this will force the build system to treat the target as satisfied after a touch or unsatisfied after an untouch:
+
+@itemize
+@item make @i{MODULE}.extract.touch
+@item make @i{MODULE}.extract.untouch
+@item make @i{MODULE}.patch.touch
+@item make @i{MODULE}.patch.untouch
+@item make @i{MODULE}.configure.touch
+@item make @i{MODULE}.configure.untouch
+@item make @i{MODULE}.build.touch
+@item make @i{MODULE}.build.untouch
+@item make @i{MODULE}.install.touch
+@item make @i{MODULE}.install.untouch
+@end itemize
+
@anchor{terminal.targets.contrib.aggregate}
@subsection Contrib Aggregates
-
For convenience, the following targets aggregate the all contrib modules' respective targets together:
@itemize