Rombobjörn

summaryrefslogtreecommitdiff
path: root/manual.en.html
diff options
context:
space:
mode:
authorBjörn Persson <bjorn@rombobjörn.se>2013-10-09 17:19:42 +0200
committerBjörn Persson <bjorn@rombobjörn.se>2013-10-09 17:19:42 +0200
commitf4b3c51803cb6e0cb915e9e84129c6d9df3352cb (patch)
treef7e8fa3cae15ca0bf4c15aa228693d777445b81b /manual.en.html
parent1cd75d10b77fbf947957a32e7d79463ac92abf0c (diff)
Moved some paragraphs back.
Diffstat (limited to 'manual.en.html')
-rwxr-xr-xmanual.en.html50
1 files changed, 25 insertions, 25 deletions
diff --git a/manual.en.html b/manual.en.html
index b27f463..d46954d 100755
--- a/manual.en.html
+++ b/manual.en.html
@@ -280,21 +280,6 @@ to create the subdirectory under <var>stage_cachedir</var>.</p></li>
install log files but you may want to create a separate subdirectory under
<var>stage_logdir</var> if your program writes its own log files.</p></li>
-<li><p>Binary libraries shall be placed in <var>Comfignat.Stage_Libdir</var>
-by build project files. Usage project files shall get the directory from the
-preprocessor symbol <var>Libdir</var>.</p></li>
-
-<li><p>Ada library information (ALI) files shall be placed under a separate
-subdirectory of <var>Comfignat.Stage_Alidir</var> by build project files. Usage
-project files shall get the directory from the preprocessor symbol
-<var>Alidir</var>.</p></li>
-
-<li><p>Other architecture-specific files shall usually be placed under a
-separate subdirectory of <var>stage_libdir</var>. (It will be the same
-subdirectory that ALI files are placed in when
-<var>alidir</var> = <var>libdir</var>.) Programs shall look for them under
-<var>Comfignat.Libdir</var>.</p></li>
-
<li><p>Ada specifications, C headers and other source files that are needed for
compilation of other software that uses your libraries shall be placed under
<var>Comfignat.Stage_Includedir</var> by build project files, usually under a
@@ -310,6 +295,21 @@ put them under a separate subdirectory of <var>stage_archincludedir</var>.
Usage project files shall get the directory from the preprocessor symbol
<var>Archincludedir</var>.</p></li>
+<li><p>Binary libraries shall be placed in <var>Comfignat.Stage_Libdir</var>
+by build project files. Usage project files shall get the directory from the
+preprocessor symbol <var>Libdir</var>.</p></li>
+
+<li><p>Ada library information (ALI) files shall be placed under a separate
+subdirectory of <var>Comfignat.Stage_Alidir</var> by build project files. Usage
+project files shall get the directory from the preprocessor symbol
+<var>Alidir</var>.</p></li>
+
+<li><p>Other architecture-specific files shall usually be placed under a
+separate subdirectory of <var>stage_libdir</var>. (It will be the same
+subdirectory that ALI files are placed in when
+<var>alidir</var> = <var>libdir</var>.) Programs shall look for them under
+<var>Comfignat.Libdir</var>.</p></li>
+
<li><p>Comfignat puts usage project files in <var>stage_gprdir</var>.</p></li>
<li><p>Locale-specific message catalogs shall be placed in the appropriate
@@ -350,6 +350,16 @@ target architecture.</dd>
<dd>The top-level directory for programs that are intended to be run by other
programs rather than by users.</dd>
+<dt><var>Includedir</var></dt>
+<dd>The top-level directory for (normally architecture-independent) source
+files to be used in the compilation of software using libraries.</dd>
+
+<dt><var>Archincludedir</var></dt>
+<dd>The parent of libraries' separate library-specific directories for
+architecture-specific source files to be used in the compilation of software
+using libraries, for any libraries that absolutely must install such
+files.</dd>
+
<dt><var>Libdir</var></dt>
<dd>The directory for binary libraries to be used by other software, and the
top-level directory for other architecture-specific files.</dd>
@@ -359,16 +369,6 @@ top-level directory for other architecture-specific files.</dd>
Ada library information files.</dd>
</dl>
-<dt><var>Includedir</var></dt>
-<dd>The top-level directory for architecture-independent source files to be
-used in the compilation of software using libraries.</dd>
-
-<dt><var>Archincludedir</var></dt>
-<dd>The parent of libraries' separate library-specific directories for
-architecture-specific source files to be used in the compilation of software
-using libraries, for any libraries that absolutely must install such
-files.</dd>
-
<p>Here's an example of what a directories project may look like:</p>
<pre class="example gpr">abstract project System_Directories is