TheCloud/panda3d
1
0
Fork 0
mirror of https://github.com/panda3d/panda3d.git synced 2025-10-03 02:15:43 -04:00
Code Issues Packages Projects Releases Wiki Activity

grammar, spelling fixups

Browse Source
This commit is contained in:
Darren Ranalli 2002-02-22 22:03:38 +00:00
parent b09d07bff8
commit 85746661ca
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
panda/src/doc/ppremake-philosophy.txt
View File

@ -59,7 +59,7 @@ WHAT IS PPREMAKE, EXACTLY?
ppremake, including the meaning of all the variables defined within ppremake, including the meaning of all the variables defined within
the various Sources.pp files (see below) and all of the generated the various Sources.pp files (see below) and all of the generated
output, is almost entirely controlled by scripts written in its own output, is almost entirely controlled by scripts written in its own
scripting language. Most of these are control scripts are defined scripting language. Most of these control scripts are defined
in the directory $DTOOL/pptempl. in the directory $DTOOL/pptempl.

6
panda/src/doc/ppremake-process.txt
View File

@ -48,7 +48,7 @@ The following steps are executed when ppremake is invoked:
needs to include. The use of System.pp to define these needs to include. The use of System.pp to define these
filenames, instead of hardcoding them into ppremake, is filenames, instead of hardcoding them into ppremake, is
consistent with the ppremake philosophy of letting as much of its consistent with the ppremake philosophy of letting as much of its
behavior as possible to be controlled from within the scripting behavior as possible be controlled from within the scripting
language itself. language itself.
3. Once Package.pp has been read, traverse the entire source 3. Once Package.pp has been read, traverse the entire source
@ -76,7 +76,7 @@ The following steps are executed when ppremake is invoked:
relationships between different directories within the source relationships between different directories within the source
hierarchy. Each directory may depend on code from zero or more hierarchy. Each directory may depend on code from zero or more
other directories within the same package. (That is, a directory other directories within the same package. (That is, a directory
may include header files define within another directory, and/or may include header files defined within another directory, and/or
require linking with a library built in that directory.) require linking with a library built in that directory.)
This inter-directory dependency is critical to determine things This inter-directory dependency is critical to determine things
@ -138,5 +138,5 @@ The following steps are executed when ppremake is invoked:
directory. Since there may be different kinds of source directory. Since there may be different kinds of source
directories, each with very different makefile requirements, the directories, each with very different makefile requirements, the
Template files usually have one large #if condition based on the Template files usually have one large #if condition based on the
value of $[DIR_TYPE], which is set within in each Sources.pp (and value of $[DIR_TYPE], which is set within each Sources.pp (and
is set in System.pp to default to "src"). is set in System.pp to default to "src").

2
panda/src/doc/ppremake-syntax.txt
View File

@ -15,7 +15,7 @@ variables defined in Global.pp and related files are declared. There
are also a number of individually named scopes, one scope for each are also a number of individually named scopes, one scope for each
directory in the source hierarchy that contains a Sources.pp file. directory in the source hierarchy that contains a Sources.pp file.
Each of these scopes is a child of the global scope, each of these Each of these scopes is a child of the global scope, each of these
defines the varibles defined within its Sources.pp file. The name of defines the variables defined within its Sources.pp file. The name of
each scope is the name of the directory, with a trailing slash. each scope is the name of the directory, with a trailing slash.
For instance, imagine the following simple directory hierarchy: For instance, imagine the following simple directory hierarchy: