Examples of ``gnatmake`` Usage
------------------------------
-*gnatmake hello.adb*
+``gnatmake hello.adb``
Compile all files necessary to bind and link the main program
:file:`hello.adb` (containing unit ``Hello``) and bind and link the
resulting object files to generate an executable file :file:`hello`.
-*gnatmake main1 main2 main3*
+``gnatmake main1 main2 main3``
Compile all files necessary to bind and link the main programs
:file:`main1.adb` (containing unit ``Main1``), :file:`main2.adb`
(containing unit ``Main2``) and :file:`main3.adb`
to generate three executable files :file:`main1`,
:file:`main2` and :file:`main3`.
-*gnatmake -q Main_Unit -cargs -O2 -bargs -l*
+``gnatmake -q Main_Unit -cargs -O2 -bargs -l``
Compile all files necessary to bind and link the main program unit
``Main_Unit`` (from file :file:`main_unit.adb`). All compilations will
be done with optimization level 2 and the order of elaboration will be
* subunits
-because they are compiled as part of compiling related units. GNAT
+because they are compiled as part of compiling related units. GNAT compiles
package specs
when the corresponding body is compiled, and subunits when the parent is
compiled.
file in any directory using an absolute or relative path specification
containing the directory information.
-TESTING: the :switch:`--foobar{NN}` switch
-
.. index:: gnat1
``gcc`` is actually a driver program that looks at the extensions of
* The content of the :file:`ada_source_path` file which is part of the GNAT
installation tree and is used to store standard libraries such as the
GNAT Run Time Library (RTL) source files.
- :ref:`Installing_a_library`
+ See also :ref:`Installing_a_library`.
Specifying the switch :switch:`-I-`
inhibits the use of the directory
$ gcc -c -O2 -gnata xyz-def.adb
Compile the child unit package in file :file:`xyz-def.adb` with extensive
-optimizations, and pragma ``Assert``/`Debug` statements
+optimizations, and pragma ``Assert``/``Debug`` statements
enabled.
.. code-block:: sh
size of the executable, compared with a traditional per-unit compilation
with inlining across units enabled by the :switch:`-gnatn` switch.
The drawback of this approach is that it may require more memory and that
- the debugging information generated by -g with it might be hardly usable.
+ the debugging information generated by ``-g`` with it might be hardly usable.
The switch, as well as the accompanying :switch:`-Ox` switches, must be
specified both for the compilation and the link phases.
If the ``n`` parameter is specified, the optimization and final code
This switch will generate an intermediate representation suitable for
use by CodePeer (:file:`.scil` files). This switch is not compatible with
code generation (it will, among other things, disable some switches such
- as -gnatn, and enable others such as -gnata).
+ as ``-gnatn``, and enable others such as ``-gnata``).
.. index:: -gnatd (gcc)
the :switch:`-gnatd` specifies the specific debug options. The possible
characters are 0-9, a-z, A-Z, optionally preceded by a dot or underscore.
See compiler source file :file:`debug.adb` for details of the implemented
- debug options. Certain debug options are relevant to applications
+ debug options. Certain debug options are relevant to application
programmers, and these are documented at appropriate points in this
- users guide.
+ user's guide.
.. index:: -gnatD[nn] (gcc)
Create expanded source files for source level debugging. This switch
also suppresses generation of cross-reference information
(see :switch:`-gnatx`). Note that this switch is not allowed if a previous
- -gnatR switch has been given, since these two switches are not compatible.
+ ``-gnatR`` switch has been given, since these two switches are not compatible.
.. index:: -gnateA (gcc)
where implicit ``pragma Elaborate`` and ``pragma Elaborate_All``
are generated. This is useful in diagnosing elaboration circularities
caused by these implicit pragmas when using the static elaboration
- model. See See the section in this guide on elaboration checking for
+ model. See the section in this guide on elaboration checking for
further details. These messages are not generated by default, and are
intended only for temporary use when debugging circularity problems.
.. index:: -gnatw_A
:switch:`-gnatw_A`
- *Supress warnings on anonymous allocators.*
+ *Suppress warnings on anonymous allocators.*
.. index:: Anonymous allocators
:switch:`-gnatw_C`
*Suppress warnings on unknown condition in Compile_Time_Warning.*
- This switch supresses warnings on a pragma Compile_Time_Warning
+ This switch suppresses warnings on a pragma Compile_Time_Warning
or Compile_Time_Error whose condition has a value that is not
known at compile time.
This switch activates warnings for declarations that declare a name that
is defined in package Standard. Such declarations can be confusing,
especially since the names in package Standard continue to be directly
- visible, meaning that use visibiliy on such redeclared names does not
+ visible, meaning that use visibility on such redeclared names does not
work as expected. Names of discriminants and components in records are
not included in this check.
git://gcc.gnu.org / gcc.git / blobdiff