/usr/share/doc/gnat-gps/html/The-Build-Menu.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 | <html lang="en">
<head>
<title>The Build Menu - 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="Compilation_002fBuild.html#Compilation_002fBuild" title="Compilation/Build">
<link rel="next" href="The-Target-Configuration-Dialog.html#The-Target-Configuration-Dialog" title="The Target Configuration Dialog">
<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="The-Build-Menu"></a>
<p>
Next: <a rel="next" accesskey="n" href="The-Target-Configuration-Dialog.html#The-Target-Configuration-Dialog">The Target Configuration Dialog</a>,
Up: <a rel="up" accesskey="u" href="Compilation_002fBuild.html#Compilation_002fBuild">Compilation/Build</a>
<hr>
</div>
<h3 class="section">9.1 The Build Menu</h3>
<p class="noindent">The build menu gives access to capabilities related to checking, parsing and
compiling files, as well as creating and running executables.
note that this menu is fully configurable via the <code>Targets</code> dialog,
so what is documented in this manual are the default menus.
<p>See <a href="The-Target-Configuration-Dialog.html#The-Target-Configuration-Dialog">The Target Configuration Dialog</a>.
<dl>
<dt><b>Check Syntax</b><dd>Check the syntax of the current source file. Display an error message in
the <i>Messages</i> window if no file is currently selected.
<br><dt><b>Check Semantic</b><dd>Check the semantic of the current source file. Display an error message in
the <i>Messages</i> window if no file is currently selected.
<br><dt><b>Compile File</b><dd>Compile the current file.
By default, will display an intermediate dialog where you can add extra
switches, or simply press <Enter> to get the standard (or previous)
switches.
Display an error message in the <i>Messages</i> window if no file is selected.
<p>If errors or warnings occur during the compilation, the corresponding locations
will appear in the Locations View. If the corresponding Preference is set, the
source lines will be highlighted in the editors (see
<a href="The-Preferences-Dialog.html#The-Preferences-Dialog">The Preferences Dialog</a>).
To remove the highlighting on these lines, remove the files from the Locations
View using either the contextual menu (<code>Remove category</code>) or by closing
the Locations View.
<br><dt><b>Project</b><dd>
<dl>
<dt><i>Build <main></i><dd> The menu will list of all mains defined in your project hierarchy.
Each menu item will build the selected main.
<br><dt><i>Build All</i><dd> Build and link all main units defined in your project.
If no main unit is specified in your project, build all files defined
in your project and subprojects recursively.
For a library project file, compile sources and recreate the library
when needed.
<br><dt><i>Compile All Sources</i><dd> Compile all source files defined in the top level project.
<br><dt><i>Build <current file></i><dd> Consider the currently selected file as a main file, and build it.
<br><dt><i>Custom Build...</i><dd> Display a text entry where you can enter any external command. This menu
is very useful when you already have existing build scripts, make files,
<small class="dots">...</small> and want to invoke them from GPS. If the <code>SHELL</code> environment
variable is defined (to e.g. <code>/bin/sh</code>), then the syntax used to
execute the command is the one for this shell. Otherwise, the command
will be spawned directly by GPS without any shell interpretation.
</dl>
<br><dt><b>Clean</b><dd>
<dl>
<dt><i>Clean All</i><dd> Remove all object files and other compilation artifacts associated to all
projects related to the current one. It allows to restart a complete build
from scratch.
<br><dt><i>Clean Root</i><dd> Remove all object files and other compilation artifacts associated to the
root project. It does not clean objects from other related projects.
</dl>
<br><dt><b>Makefile</b><dd>If you have a file called <samp><span class="file">Makefile</span></samp> in the same directory as your
project file is, or if you've set the <code>makefile</code> property in the
<code>Make</code> section of the project properties (see
<a href="The-Project-Properties-Editor.html#The-Project-Properties-Editor">The Project Properties Editor</a>), this menu will be displayed, giving
access to all the targets defined in your makefile.
<br><dt><b>Run</b><dd>
<dl>
<dt><i>main</i><dd> For each main source file defined in your top level project, an entry
is listed to run the executable associated with this main file.
Running an application will first open a dialog where you can specify
command line arguments to your application, if needed. You can also
specify whether the application should be run within GPS (the default),
or using an external terminal.
<p>When running an application from GPS, a new execution window is added in the
bottom area where input and output of the application is handled. This
window is never closed automatically, even when the application terminates,
so that you can still have access to the application's output. If you
explicitly close an execution window while an application is still running,
a dialog window will be displayed to confirm whether the application should
be terminated.
<p>When using an external terminal, GPS launches an external terminal
utility that will take care of the execution and input/output of your
application. This external utility can be configured in the preferences
dialog (<i>External Commands->Execute command</i>).
<p>The GPS execution windows have several limitations compared to external
terminals. In particular, they do not handle signals like <ctrl-z>
and <control-c>. In general, if you are running an interactive
application, we strongly encourage you to run in an external terminal.
<p>Similarly, the <code>Run</code> contextual menu accessible from a project
entity contains the same entries.
<br><dt><i>Custom...</i><dd> Similar to the entry above, except that you can run any arbitrary executable.
If the <code>SHELL</code> environment
variable is defined (to e.g. <code>/bin/sh</code>), then the syntax used to
execute the command is the one for this shell. Otherwise, the command
will be spawned directly by GPS without any shell interpretation.
</dl>
<br><dt><b>Recompute Xref info</b><dd><a name="index-C-422"></a><a name="index-C_002b_002b-423"></a>Recompute the cross-reference information for Ada, C and C++ source files.
See <a href="Support-for-Cross_002dReferences.html#Support-for-Cross_002dReferences">Support for Cross-References</a>.
<br><dt><b>Load xref info in memory</b><dd><a name="index-C-424"></a><a name="index-C_002b_002b-425"></a>Load all the cross-reference information in memory. This menu is generally
not needed, See <a href="Support-for-Cross_002dReferences.html#Support-for-Cross_002dReferences">Support for Cross-References</a>.
<br><dt><b>Settings</b><dd>
<dl>
<dt><i>Targets</i><dd> <a name="index-Targets-426"></a> This opens the Target Configuration Dialog.
See <a href="The-Target-Configuration-Dialog.html#The-Target-Configuration-Dialog">The Target Configuration Dialog</a>.
<br><dt><i>Toolchains</i><dd> <a name="index-Toolchains-427"></a> Open a dialog allowing the configuration of GPS for working with two
compilation toolchains. This is particulary useful when compiling a
project with an old compiler, while wanting up-to-date functionalities
from the associated tools (gnatmetric, gnatcheck and so on).
See <a href="Working-with-two-compilers.html#Working-with-two-compilers">Working with two compilers</a>.
</dl>
</dl>
<p>The <code>Tools->Interrupt</code> menu can be used to interrupt the last compilation
or run command. Once you have interrupted that last operation, you can
interrupt the previous one by selecting the same menu again.
<p>However, the easiest way to interrupt a specific operation, no matter if it was
started last or not, is to use the <code>Task Manager</code>, through the
<code>Tools->Views->Tasks</code> menu. It will show one line per running process,
and right-clicking on any of these lines gives the possibility to interrupt
that process.
<p>If your application is build through a Makefile, you should probably load
the <samp><span class="file">Makefile.py</span></samp> startup script (see the menu <code>/Tools/Plug-ins</code>).
</body></html>
|