/usr/share/doc/gnat-gps/html/Description-of-the-Projects.html is in gnat-gps-doc 5.0-6.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 | <html lang="en">
<head>
<title>Description of the Projects - Using the GNAT Programming Studio</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Using the GNAT Programming Studio">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Project-Handling.html#Project-Handling" title="Project Handling">
<link rel="next" href="Supported-Languages.html#Supported-Languages" title="Supported Languages">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
Copyright (C) 2002-2010 AdaCore.
This document is free; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.
This document is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, see `http://www.gnu.org/licenses/'.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
pre.smallexample {background-color:rgb(240,240,240);
font-family: courier new,courier,fixed;
font-size: 14px;
margin: 0px 40px 0px 40px;
border-width: 1px 2px 2px 1px;
border-top-style: dotted;
border-left-style: dotted;
border-right-style: solid;
border-bottom-style: solid;
border-color: black;}
code {color:black;
font-family: courier new,courier,fixed;
font-size: 14px;}
body {font-family: arial,helvetica,sans-serif;
font-size: 16px;
max-width: 800px;
text-align: justify}
samp {font-family: courier new,courier,fixed;
font-size: 14px}
--></style>
</head>
<body>
<div class="node">
<a name="Description-of-the-Projects"></a>
<p>
Next: <a rel="next" accesskey="n" href="Supported-Languages.html#Supported-Languages">Supported Languages</a>,
Up: <a rel="up" accesskey="u" href="Project-Handling.html#Project-Handling">Project Handling</a>
<hr>
</div>
<h3 class="section">7.1 Description of the Projects</h3>
<p><a name="index-project-description-314"></a><!-- -->
<h4 class="subsection">7.1.1 Project files and GNAT tools</h4>
<p><a name="index-project-file-315"></a><a name="index-GNAT-316"></a>
This section describes what the projects are, and what information
they contain.
<p>The most important thing to note is that the projects used by GPS are
the same as the ones used by GNAT. These are text files (using the
extension <samp><span class="file">.gpr</span></samp>) which can be edited either manually, with any
text editor, or through the more advanced GPS interface.
<p>The exact syntax of the project files is fully described in the GNAT
User's Guide (<a href="gnat_ug.html">gnat_ug.html</a>) and GNAT Reference Manual
(<a href="gnat_rm.html">gnat_rm.html</a>). This is recommended reading if you want to use
some of the more advanced capabilities of project files which are not
yet supported by the graphical interface.
<p>GPS can load any project file, even those that you have been
edited manually. Furthermore, you can manually edit project files
created by GPS.
<p>Typically you will not need to edit project files manually, since several
graphical tools such as the project wizard (<a href="The-Project-Wizard.html#The-Project-Wizard">The Project Wizard</a>)
and the properties editor(<a href="The-Project-Properties-Editor.html#The-Project-Properties-Editor">The Project Properties Editor</a>) are
provided.
<p><a name="index-normalization-of-projects-317"></a>GPS doesn't preserve the layout nor comments of manually created
projects after you have edited them in GPS. For instance, multiple case
statements in the project will be coalesced into a single case statement.
This normalization is required for GPS to be able to preserve the previous
semantic of the project in addition to the new settings.
<p><a name="index-GNAT-318"></a>All command-line GNAT tools are project aware, meaning that the notion
of project goes well beyond GPS' user interface. Most capabilities
of project files can be accessed without using GPS itself, making
project files very attractive.
<p><a name="index-ADA_005fPROJECT_005fPATH-319"></a>GPS uses the same mechanisms to locate project files as GNAT
itself:
<ul>
<li>absolute paths
<li>relative paths.
These paths, when used in a with line as described below, are relative
to the location of the project that does the with.
<li>ADA_PROJECT_PATH.
If this environment variable is set, it contains a colon-separated (or
semicolon under Windows) list of directories in which the project files are
searched.
<li>predefined project path.
The compiler itself defines a predefined project path, in which standard
libraries can be installed, like XML/Ada for instance.
</ul>
<h4 class="subsection">7.1.2 Contents of project files</h4>
<p><a name="index-project-file-320"></a>
Project files contain all the information that describe the
organization of your source files, object files and executables.
<p><a name="index-project-comments-321"></a>A project file can contain comments, which have the same format as in Ada,
that is they start by "–" and extend to the end of the line.
You can add comments when you edit the project file manually. GPS will
attempt to preserve them when you save the project through the menu, but this
will not always be possible. It helps if the comments are put at the end of
the line, as in
<pre class="smallexample"> project Default is
for Source_Dirs use (); -- No source in this project
end Default;
</pre>
<p><a name="index-sub-project-322"></a>Generally, one project file will not be enough to describe a complex
organization. In this case, you will create and use a project hierarchy,
with a root project importing other sub projects. Each of the projects
and sub projects is responsible for its own set of sources (compiling
them with the appropriate switches, put the resulting files in the
right directories, <small class="dots">...</small>).
<p><a name="index-GNAT-323"></a>Each project contains the following information
(see the GNAT user's guide for the full list)
<ul>
<li><b>List of imported projects</b>:
<a name="index-imported-project-324"></a> When you are compiling sources from this project, the compiler
(either through GNAT or the automatically generated Makefiles) will
first make sure that all the imported projects have been correctly
recompiled and are up-to-date. This way, dependencies between
source files are properly handled.
<p>If one of the source files of project A depends on some source
files from project B, then B must be imported by A. If this isn't
the case, the compiler will complain that some of the source files
cannot be found.
<p>One important rule is that each source file name must be unique in
the project hierarchy (i.e. a file cannot be under control of two
different projects). This ensures that the same file will be found
no matter what project is managing the source file that uses
<li><b>List of source directories</b>:
<a name="index-source-directory-325"></a> All the sources managed by a project are found in one or more
source directories. Each project can have multiple source
directories, and a given source directory might be shared by
multiple projects.
<li><b>Object directory</b>:
<a name="index-object-directory-326"></a> When the sources of the project are compiled, the resulting object
files are put into this object directory. There exist exactly one object
directory for each project. If you need to split the object files
among multiple object directories, you need to create multiple
projects importing one another as appropriate.
<p>When sources from imported sub-projects are recompiled, the
resulting object files are put in the sub project's own object
directory, and will never pollute the parent's object directory.
<li><b>Exec directory</b>:
<a name="index-exec-directory-327"></a> When a set of object files is linked into an executable, this executable
is put in the exec directory of the project file. If this attribute
is unspecified, the object directory is used.
<li><b>List of source files</b>:
<a name="index-source-file-328"></a> The project is responsible for managing a set of source
files. These files can be written in any programming
languages. Currently, the graphical interface supports Ada, C and C++.
<p>The default to find this set of source files is to take all the
files in the source directories that follow the naming scheme (see
below) for each language. In addition if you edit the
project file manually, it is possible to provide an explicit list of source
files.
<p>This attribute cannot be modified graphically yet.
<li><b>List of main units</b>:
<a name="index-main-unit-329"></a> The main units of a project (or main files in some languages) are
the units that contain the main subprogram of the application, and
that can be used to link the rest of the application.
<p>The name of the file is generally related to the name of the
executable.
<p>A given project file hierarchy can be used to compile and link
several executables. GPS will automatically update the Compile, Run
and Debug menu with the list of executables, based on this list.
<li><b>Naming schemes</b>:
<a name="index-naming-scheme-330"></a> The naming scheme refers to the way files are named for each
languages of the project. This is used by GPS to choose the language
support to use when a source file is opened. This is also used to
know what tools should be used to compile or otherwise work with a
source file.
<li><b>Embedded targets and cross environments</b>:
<a name="index-cross-environment-331"></a> GPS supports cross environment software development: GPS itself can
run on a given host, such as GNU/Linux, while compilations, runs and
debugging occur on a different remote host, such as Sun/Solaris.
<p><a name="index-VxWorks-332"></a> GPS also supports embedded targets (VxWorks, <small class="dots">...</small>) by specifying
alternate names for the build and debug tools.
<p>The project file contains the information required to log on the
remote host.
<li><b>Tools</b>:
<a name="index-tools-333"></a> Project files provide a simple way to specify the compiler and
debugger commands to use.
<li><b>Switches</b>:
<a name="index-switches-334"></a> Each tool that is used by GPS (compiler, pretty-printer, debugger,
<small class="dots">...</small>) has its own set of switches. Moreover, these switches may
depend on the specific file being processed, and the programming
language it is written in.
</ul>
<!-- -->
</body></html>
|