small documentation update (nothing important).

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@93536 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/doc/CODING-GUIDELINES b/doc/CODING-GUIDELINES
index fb4e60ae6ffe7531a7da8dc1d99f07b32d60d21f..a0b19962ab67f88c9d7733c6736949cc5cf8df91 100644 (file)
--- a/doc/CODING-GUIDELINES
+++ b/doc/CODING-GUIDELINES
@@ -628,11 +628,12 @@ headers. Please update this file if you add new headers.
            ==  PART TWO: BUILD ARCHITECTURE  ==
            ------------------------------------
 
-The asterisk build architecture relies on 'autoconf' to detect the
+The asterisk build architecture relies on autoconf to detect the
 system configuration, and on a locally developed tool (menuselect) to
 select build options and modules list, and on gmake to do the build.
 
-autoconf will store its findings in two files:
+The first step, usually to be done soon after a checkout, is running
+"./configure", which will store its findings in two files:
 
     + include/asterisk/autoconfig.h
        contains C macros, normally #define HAVE_FOO or HAVE_FOO_H ,
@@ -649,7 +650,10 @@ autoconf will store its findings in two files:
        FOO_DIR=... indicating, for each package, the useful libraries
        and header files. 
 
+The next step is to run "menuselect", to extract the dependencies existing
+between files and modules, and to store build options.
 menuselect produces two files, both to be read by the Makefile:
+
     + menuselect.makeopts
        contains for each subdirectory a list of modules that must be
        excluded from the build, plus some additional informatiom.