From: Michal Vaner <vorner@ucw.cz>
Date: Sat, 13 Sep 2008 20:51:18 +0000 (+0200)
Subject: free docs: explain where the variables come from
X-Git-Tag: holmes-import~227^2~5^2~40
X-Git-Url: http://mj.ucw.cz/gitweb/?a=commitdiff_plain;h=d2c2b192f46171d3db87679e0af0259b4c3b7662;p=libucw.git

free docs: explain where the variables come from

The variables in configuration preprocessing (the compile time ones from
configure script)
---

diff --git a/ucw/doc/config.txt b/ucw/doc/config.txt
index 5d655d7b..760f8651 100644
--- a/ucw/doc/config.txt
+++ b/ucw/doc/config.txt
@@ -160,9 +160,10 @@ Preprocessing
 During compilation, all configuration files are pre-processed by a simple
 C-like preprocessor, which supports `#ifdef`, `#ifndef`, `#if`,
 `#elsif`, `#else` and `#endif` directives referring to compile-time
-configuration variables. `#if` and `#elsif` can contain any Perl expression
-where each `CONFIG_xyz` configuration variable is substituted to 0 or 1
-depending on its value.
+configuration variables (the ones detected by `configure` script, you
+can see list of them in `obj/autoconf.h`). `#if` and `#elsif` can contain
+any Perl expression where each `CONFIG_xyz` configuration variable is
+substituted to 0 or 1 depending on its value.
 
 The preprocessor also substitutes `@VARIABLE@` by the value of the variable,
 which must be defined.