From: Fred Drake <fdrake@acm.org>
Date: Thu, 29 Apr 1999 02:44:50 +0000 (+0000)
Subject: Clarify that the Modules/ directory is in an unpacked source
X-Git-Tag: v1.6a1~1422
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a4a90ddeac5f5a9a3476adb79bbac28ed1464438;p=thirdparty%2FPython%2Fcpython.git

Clarify that the Modules/ directory is in an unpacked source
distribution; this is not clear for Windows users.
---

diff --git a/Doc/ext/ext.tex b/Doc/ext/ext.tex
index cda1b2d9b919..3c7fae9975fc 100644
--- a/Doc/ext/ext.tex
+++ b/Doc/ext/ext.tex
@@ -420,15 +420,15 @@ If you can't use dynamic loading, or if you want to make your module a
 permanent part of the Python interpreter, you will have to change the
 configuration setup and rebuild the interpreter.  Luckily, this is
 very simple: just place your file (\file{spammodule.c} for example) in
-the \file{Modules} directory, add a line to the file
-\file{Modules/Setup.local} describing your file:
+the \file{Modules/} directory of an unpacked source distribution, add
+a line to the file \file{Modules/Setup.local} describing your file:
 
 \begin{verbatim}
 spam spammodule.o
 \end{verbatim}
 
 and rebuild the interpreter by running \program{make} in the toplevel
-directory.  You can also run \program{make} in the \file{Modules}
+directory.  You can also run \program{make} in the \file{Modules/}
 subdirectory, but then you must first rebuild \file{Makefile}
 there by running `\program{make} Makefile'.  (This is necessary each
 time you change the \file{Setup} file.)