From c2e343aede23579a76c02469e5594410928ee563 Mon Sep 17 00:00:00 2001 From: Björn Persson Date: Fri, 18 Oct 2013 18:57:19 +0200 Subject: additions to the manual --- manual.en.html | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/manual.en.html b/manual.en.html index e54dda0..59bd42b 100755 --- a/manual.en.html +++ b/manual.en.html @@ -96,7 +96,8 @@ this.

GNU Make that may not be supported by other clones and forks of Make. If a system's native Make doesn't have those features and GNU Make isn't available, then it's possible to bypass Make and run first Gnatprep and then Gnatmake or -GPRbuild manually. It's less convenient to build that way though, and some of +GPRbuild manually. It's less convenient to build that way though, files that the +GNAT tools don't handle must then be installed in some other way, and some of the features listed here are lost.

@@ -522,6 +523,22 @@ root of the source tree. Here's an example:

Writing Make Rules

+

Building GNAT Projects

+ +

The projects that are listed in build_GPRs will be built by +default. Any other project needs a rule to control when it is built. Such a +rule shall use the variable build_GPR in its recipe. +build_GPR contains a command that performs a build controlled by the +first project file among the rule's prerequisites. The command is affected by +program-name and options variables, along with +builder_arguments and options. +A library that comes with some demo programs might have a rule like this to +build the demos only on explicit request (also ensuring that the library has +been built first):

+ +
demo_programs: demos.gpr build
+	${build_GPR}
+

Making Directories

There is no need to write rules to make directories. Comfignat has a pattern -- cgit v1.2.3