summaryrefslogtreecommitdiff
path: root/docs/README.xhtml
diff options
context:
space:
mode:
authorLuke Shumaker <LukeShu@sbcglobal.net>2009-07-13 16:07:25 -0400
committerLuke Shumaker <lukeshu@sbcglobal.net>2015-06-26 00:30:11 -0600
commit1a65ae278e81946ec3a8af43b1f6f18c26e1161a (patch)
treeb08ab355f44ca036ff4e9743966454d5df1a1e09 /docs/README.xhtml
parent1f75a1dff61a33dea973ebeea64a3bd8bccb715a (diff)
rvs-0.6.1 -- make it possible to compile from another directory
Diffstat (limited to 'docs/README.xhtml')
-rw-r--r--docs/README.xhtml6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/README.xhtml b/docs/README.xhtml
index ded2de0..e74e2b8 100644
--- a/docs/README.xhtml
+++ b/docs/README.xhtml
@@ -89,12 +89,12 @@
<li>one can use any lanugage to write new modules, without having to worry about bindings</li>
</ol>
<h3>build system</h3>
-<p>The build system rvs uses is rather simple. <kbd>./configure</kbd> does 2 things, create a preprocessor in <kbd>tmp/var.sed</kbd>, and generate a <kbd>Makefile</kbd> with this preprocessor from <a href="../Makefile.orig"><kbd>Makefile.orig</kbd></a>. Then, the <kbd>Makefile</kbd> (among other things), runs each source file through the preprocessor.</p>
+<p>The build system rvs uses is rather simple. <kbd>./configure</kbd> does 2 things, create a preprocessor in <kbd>tmp/var.sed</kbd>, and generate a <kbd>Makefile</kbd> with this preprocessor from <a href="../Makefile.orig"><kbd>Makefile.orig</kbd></a>. Then, the <kbd>Makefile</kbd> (among other things), runs each source file through the preprocessor.</p>
<h4>preprocessor/variables</h4>
-<p>You know the configuration variables described in <a href="../README"><kbd>README</kbd></a>? Part of the build process involves running all source files through a pre-processor (kept in <kbd>tmp/var.sed</kbd>). This preproccessor allows you to reference the configuration variables in any file in <kbd>source/</kbd> or <a href="../Makefile"><kbd>Makefile</kbd></a>. Any instance of <samp>$$VAR_NAME$$</samp> will be repleced by the value of the variable.</p>
+<p>You know the configuration variables described in <a href="../README"><kbd>README</kbd></a>? Part of the build process involves running all source files through a pre-processor (kept in <kbd>tmp/var.sed</kbd>). This preproccessor allows you to reference the configuration variables in any file in <kbd>source/</kbd> or <a href="../Makefile"><kbd>Makefile</kbd></a>. Any instance of <samp>$$VAR_NAME$$</samp> will be repleced by the value of the variable. Note that only defined variables will be replaced.</p>
<h3>known bugs</h3>
<ul>
- <li>borks on files with the newline character. The smart thing to do would be to escape all speacial characters.
+ <li>borks on files with the newline character. The smart thing to do would be to escape all speacial characters.
<br />Files to be changed:<ul>
<li><kbd>soruce/rvs-core/commit</kbd></li>
<li><kbd>soruce/rvs-core/commit.d</kbd></li>