2009-10-01 Tobias Burnus <burnus@net-b.de>
[official-gcc/alias-decl.git] / gcc / ada / gnatcmd.ads
blob6c2c8c7f50f3a105f8bcd15008051a8232f1bf49
1 ------------------------------------------------------------------------------
2 -- --
3 -- GNAT COMPILER COMPONENTS --
4 -- --
5 -- G N A T C M D --
6 -- --
7 -- S p e c --
8 -- --
9 -- Copyright (C) 1996-2008, Free Software Foundation, Inc. --
10 -- --
11 -- GNAT is free software; you can redistribute it and/or modify it under --
12 -- terms of the GNU General Public License as published by the Free Soft- --
13 -- ware Foundation; either version 3, or (at your option) any later ver- --
14 -- sion. GNAT is distributed in the hope that it will be useful, but WITH- --
15 -- OUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY --
16 -- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License --
17 -- for more details. You should have received a copy of the GNU General --
18 -- Public License distributed with GNAT; see file COPYING3. If not, go to --
19 -- http://www.gnu.org/licenses for a complete copy of the license. --
20 -- --
21 -- GNAT was originally developed by the GNAT team at New York University. --
22 -- Extensive contributions were provided by Ada Core Technologies Inc. --
23 -- --
24 ------------------------------------------------------------------------------
26 -- This program provides a simple command interface for using GNAT and its
27 -- associated utilities. The format of switches accepted is intended to
28 -- be more familiar in style for VMS and DOS users than the standard Unix
29 -- style switches that are accepted directly.
31 -- The program is typically called GNAT when it is installed and
32 -- the two possible styles of use are:
34 -- To call gcc:
36 -- GNAT filename switches
38 -- To call the tool gnatxxx
40 -- GNAT xxx filename switches
42 -- where xxx is the command name (e.g. MAKE for gnatmake). This command name
43 -- can be abbreviated by giving a prefix (e.g. GNAT MAK) as long as it
44 -- remains unique.
46 -- In both cases, filename is in the format appropriate to the operating
47 -- system in use. The individual commands give more details. In some cases
48 -- a unit name may be given in place of a file name.
50 -- The switches start with a slash. Switch names can also be abbreviated
51 -- where no ambiguity arises. The switches associated with each command
52 -- are specified by the tables that can be found in the body.
54 -- Although by convention we use upper case for command names and switches
55 -- in the documentation, all command and switch names are case insensitive
56 -- and may be given in upper case or lower case or a mixture.
58 procedure GNATCmd;