From: Michal Sojka <sojkam1@fel.cvut.cz>
Date: Tue, 21 Sep 2010 20:38:24 +0000 (+0200)
Subject: doc: Reformulation of "Dependency Tracking"
X-Git-Url: http://rtime.felk.cvut.cz/gitweb/omk.git/commitdiff_plain/b9c630c599e273e448f5db4825679b8d1fb34779

doc: Reformulation of "Dependency Tracking"
---

diff --git a/doc/omk-manual.texinfo b/doc/omk-manual.texinfo
index 7849dc2..2f6beed 100644
--- a/doc/omk-manual.texinfo
+++ b/doc/omk-manual.texinfo
@@ -557,10 +557,10 @@ You can instruct OMK to descend to a (sub)directory by setting the
 @node Dependency Tracking, Configuration and Conditional Compilation, Multiple Directories, User's Manual
 @section Dependency Tracking
 
-OMK automatically handles tracking of dependencies of files in compiled
-projects. It uses gcc's @option{-M@var{x}} options to do this for object
-files. This way, whenever you change some header file, OMK recompiles
-only those files, where the changed header was really included.
+OMK automatically tracks dependencies of files in the project.
+Dependencies of object files are produced with gcc's @option{-M@var{x}}
+options. This means that whenever a header file is changed, OMK
+recompiles only those files, which included that file.
 
 Dependencies are also maintained for libraries and binaries. To find the
 dependencies, OMK parses linker map files, so a change to some library