diff options
| -rwxr-xr-x | manual.en.html | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/manual.en.html b/manual.en.html index 03052f1..70703e4 100755 --- a/manual.en.html +++ b/manual.en.html @@ -31,7 +31,7 @@ build system can install the whole software package, not just the compiled files. At the same time Comfignat greatly reduces the amount of Make code that needs to be written for every new project.</p> -<h2>Features</h2> +<h2 id="features">Features</h2> <ul> <li><p>Users and distributions can build and install the software with the @@ -100,14 +100,14 @@ GPRbuild manually. It's less convenient to build that way though, and some of the features listed here are lost.</p></li> </ul> -<h2>Download</h2> +<h2 id="download">Download</h2> <p>The code is available for download <a href="https://www.xn--rombobjrn-67a.se/Comfignat/download">as a tarball</a>, and is also browsable <a href="https://gitorious.org/comfignat/comfignat/trees/master">on Gitorious</a>.</p> -<h3>License</h3> +<h3 id="license">License</h3> <p>The following applies to all of Comfignat including this document:</p> @@ -122,7 +122,7 @@ Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.</p> -<h2>Getting Started</h2> +<h2 id="quickstart">Getting Started</h2> <p>This is the least that you have to do to use Comfignat:</p> @@ -170,7 +170,7 @@ after preprocessing. That's all that is required of the makefile. Everything else is optional.</p></li> </ul> -<h3>Example</h3> +<h3 id="quickstart_example">Example</h3> <p>Here's a complete set of project files and makefile containing everything that is necessary for building an uncomplicated shared library and installing @@ -210,9 +210,9 @@ end Example;</pre></div> build_GPRs = build_example.gpr usage_GPRs = example.gpr</pre></div> -<h2>How to Use Comfignat</h2> +<h2 id="howto">How to Use Comfignat</h2> -<h3>Where to Place Files</h3> +<h3 id="where">Where to Place Files</h3> <p>During the build, the files that will be installed are collected in a directory structure under a staging directory whose name is held in the @@ -309,7 +309,7 @@ subdirectories under <var>stage_mandir</var>.</p></li> <var>stage_miscdocdir</var>.</p></li> </ul> -<h3>Directories Projects</h3> +<h3 id="directories_projects">Directories Projects</h3> <p>A directories project is a GNAT project file that defines directory variables for use by other project files. It may be defined by an operating @@ -372,7 +372,7 @@ project will therefore automatically adapt to the current target architecture, so that 32-bit and 64-bit instances of the library can be installed in parallel and the right library will be used in every build.</p> -<h3>Options</h3> +<h3 id="options">Options</h3> <p>Your software may have optional features or properties that can be enabled or disabled at build time. Comfignat can help you define options for those. @@ -394,7 +394,7 @@ atomic_doodads = true</pre> symbols to preprocessed files and as external variables to build project files.</p> -<h3>Build Tools and their Arguments</h3> +<h3 id="build_tools">Build Tools and their Arguments</h3> <p>There are several options variables that let installing users and distributions control which arguments the build tools are invoked with. They @@ -421,7 +421,7 @@ with Gnatmake instead of GPRbuild by default, but again be sure to do the assignment with "<samp>?=</samp>" so that environment variables can override your default.</p> -<h3>Persistent Configuration</h3> +<h3 id="configuration">Persistent Configuration</h3> <p>Those Make variables that installing users are expected to change can be configured persistently. Run "<samp>make configure</samp>" with some variables @@ -436,7 +436,7 @@ of "<samp>make distclean</samp>".</p> are included. You can make additional variables configurable by appending their names to <var>configuration_variables</var>.</p> -<h3>Separate Build Directories</h3> +<h3 id="build_directories">Separate Build Directories</h3> <p>Instead of building in the source tree you can use a separate build directory. All generated files will then be written under the build directory @@ -465,7 +465,7 @@ root of the source tree. Here's an example:</p> <pre class="example gpr">for Source_Dirs use ($Srcdir & "/tools");</pre> -<h3>Adjusting the Installation Instructions</h3> +<h3 id="installation_instructions">Adjusting the Installation Instructions</h3> <p>After writing your makefile and project files, you should adapt the installation instructions in <var>INSTALL</var> to your project. The file will |