gnat-gps-doc 5.0-6 / usr / share / doc / gnat-gps / html / Customizing-your-Projects.html

This file is indexed.

/usr/share/doc/gnat-gps/html/Customizing-your-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
<html lang="en">
<head>
<title>Customizing your 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="Working-in-a-Cross-Environment.html#Working-in-a-Cross-Environment" title="Working in a Cross Environment">
<link rel="next" href="Debugger-Issues.html#Debugger-Issues" title="Debugger Issues">
<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="Customizing-your-Projects"></a>
<p>
Next:&nbsp;<a rel="next" accesskey="n" href="Debugger-Issues.html#Debugger-Issues">Debugger Issues</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Working-in-a-Cross-Environment.html#Working-in-a-Cross-Environment">Working in a Cross Environment</a>
<hr>
</div>

<h3 class="section">14.1 Customizing your Projects</h3>

<p><a name="index-project-627"></a>
This section describes some possible ways to customize your projects when
working in a cross environment. For more details on the project capabilities,
see <a href="Project-Handling.html#Project-Handling">Project Handling</a>.

   <p>When using the project editor to modify the project's properties, two
areas are particularly relevant to cross environments:
<code>Cross environment</code> part of the <code>General</code> page, and
<code>Toolchains</code> part of the <code>Languages</code> page.

   <p>In the <code>Toolchains</code> section, you will typically either scan your system
to display found toolchains, and select the one corresponding to your cross
environment or use the Add button and manually select the desired cross
environment.

   <p>If needed, you can also modify manually some of the tools defined in this
toolchain in the <code>Details</code> part of the <code>Languages</code> page.

   <p>For example, assuming you have an Ada project, and using a powerpc VxWorks
configuration. Hitting the scan button, you should see the toolchain
<code>powerpc-wrs-vxworks</code> appearing in the <code>Toolchains</code> section. 
Selecting this toolchain will change the <code>Details</code> part, displaying the
relevant tools (e.g. <i>Gnatls</i> to
<code>powerpc-wrs-vxworks-gnatls</code> and <i>Debugger</i> to
<code>powerpc-wrs-vxworks-gdb</code> <small class="dots">...</small>).

   <p>The list of toolchains and their default values that can be selected when using
the Add button can be modified via a custom xml file. See
<a href="Customizing-and-Extending-GPS.html#Customizing-and-Extending-GPS">Customizing and Extending GPS</a> and in particular
<a href="Toolchains-customization.html#Toolchains-customization">Toolchains customization</a> for further information.

   <p>If you are using an alternative run time, e.g. a <i>soft float</i> run time,
you need to add the option <code>--RTS=soft-float</code> to the <i>Gnatls</i>
property, e.g: <code>powerpc-wrs-vxworks-gnatls --RTS=soft-float</code>, and
add this same option to the <i>Make</i> switches in the switch editor. 
See <a href="Switches.html#Switches">Switches</a> for more details on the switch editor.

   <p>To modify your project to support configurations such as multiple targets,
or multiple hosts, you can create scenario variables, and modify the setting
of the Toolchains parameters based on the value of these variables. See
<a href="Scenarios-and-Configuration-Variables.html#Scenarios-and-Configuration-Variables">Scenarios and Configuration Variables</a> for more information on these
variables.

   <p>For example, you may want to create a variable called <code>Target</code> to handle
the different kind of targets handled in your project:

     <dl>
<dt><b>Target</b><dd>   Native, Embedded
<br><dt><b>Target</b><dd>   Native, PowerPC, M68K
</dl>

   <p>Similarly, you may define a <code>Board</code> variable listing the different
boards used in your environment and change the <i>Program host</i> and <i>Protocol</i>
settings accordingly.

   <p>In some cases, it is useful to provide a different body file for a given
package (e.g. to handle target specific differences). A possible approach
in this case is to use a configuration variable (e.g. called <code>TARGET</code>),
and specify a different naming scheme for this body file (in the project
properties, <code>Naming</code> tab), based on the value of <code>TARGET</code>.

   </body></html>

APT Browse - Built by Thomas Orozco.