From d2c2b192f46171d3db87679e0af0259b4c3b7662 Mon Sep 17 00:00:00 2001 From: Michal Vaner Date: Sat, 13 Sep 2008 22:51:18 +0200 Subject: [PATCH] free docs: explain where the variables come from The variables in configuration preprocessing (the compile time ones from configure script) --- ucw/doc/config.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) 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. -- 2.39.2