diff options
author | Juergen Borleis <jbe@pengutronix.de> | 2016-06-08 17:59:59 +0200 |
---|---|---|
committer | Michael Olbrich <m.olbrich@pengutronix.de> | 2016-06-20 15:04:51 +0200 |
commit | 51d8c4125c9d3292dddf9aa44aaaad0f945431ce (patch) | |
tree | 07bd3277566b41d17538a020afca5cd8ee91f966 | |
parent | e68a03ec7872501502cf28ae1fb2007fc3d7a5df (diff) | |
download | ptxdist-51d8c4125c9d3292dddf9aa44aaaad0f945431ce.tar.gz ptxdist-51d8c4125c9d3292dddf9aa44aaaad0f945431ce.tar.xz |
Fix the meaning of this sentence
Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
-rw-r--r-- | doc/dev_manual.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/dev_manual.rst b/doc/dev_manual.rst index 410c58315..f6d0458a3 100644 --- a/doc/dev_manual.rst +++ b/doc/dev_manual.rst @@ -829,7 +829,7 @@ order. For example some kind of package would also build some X related tools, if X libraries are found. In this case it depends on the build order, if the X related tools are built or not. All the autocheck features are problematic here. So, if we do not want ``configure`` to -guess its settings we **must disable everything we do want**. +guess its settings we **must disable everything we do not want**. Since every optional parameter adds four lines of code to the rule files, PTXdist provides some shortcuts to handle it. Refer to section |