/usr/share/doc/gnat-gps/html/Paths-settings.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 | <html lang="en">
<head>
<title>Paths settings - 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="Setup-the-remote-servers.html#Setup-the-remote-servers" title="Setup the remote servers">
<link rel="prev" href="Connection-settings.html#Connection-settings" title="Connection settings">
<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="Paths-settings"></a>
<p>
Previous: <a rel="previous" accesskey="p" href="Connection-settings.html#Connection-settings">Connection settings</a>,
Up: <a rel="up" accesskey="u" href="Setup-the-remote-servers.html#Setup-the-remote-servers">Setup the remote servers</a>
<hr>
</div>
<h4 class="subsection">15.2.3 Paths settings</h4>
<!-- -->
<p>The last configuration part defines the path translations between
your local host and the remote server.
<p>The remote paths definition will allow GPS to translate your locally loaded
project (the project that resides in your local filesystem) to
paths used on the remote server. This part also tells GPS how to keep
those paths synchronized between the local machine and the remote server.
<p>All your project's dependencies must then reside in a path that is defined
here. Note that you can retrieve those paths by using <code>gnat list
-v -Pyour_project</code>. In particular, the path to the GNAT run-time
(<code>adainclude</code> directory) needs to be mapped so that code completion and
source navigation work properly on run-time entities.
<p>To add a new path, click on the <code>+</code> button, and enter the corresponding
local and remote paths.
<p>You can easily select the desired paths by clicking on the icon next
to the path's entry. Remote browsing is allowed only when the
connection configuration is set (See <a href="Connection-settings.html#Connection-settings">Connection settings</a>.) Clicking
on <code>Apply</code> will apply your connection configuration and allow you
to browse the remote host to select the remote paths.
<p>Five kinds of path synchronization can be set for each defined path:
<ul>
<li><code>Never</code>: no synchronization is required from GPS, the paths
are shared using an OS mechanism like NFS.
<li><code>Manually</code>: synchronization is needed, but will only be performed
manually using the remote view buttons.
<li><code>Always</code>: Relevant to source and object paths of your project.
They are kept synchronised by GPS before and after every remote action (such
as performing a build or run).
<li><code>Once to local</code>/<code>Once to remote</code>: Relevant to project's
dependencies. They are synchronized once when a remote project is
loaded or when a local project is set remote. They can still be
manually synchronized using the Remote View (See <a href="The-remote-view.html#The-remote-view">The remote view</a>.)
</ul>
<p>The way those paths need to be configured depends on your network architecture.
<ul>
<li>If your project is on a filesystem that is shared between your host and
the remote host (using NFS of SMB filestems, for example), then only the roots
of those filesystems need to be specified, using each server's native paths (on
Windows, the paths will be expressed using X:\my\mounted\directory\ while on
unix, the paths will be expressed using /mnt/path/).
<li>If the project's files are synchronized using rsync, defining a too generic
path translation will lead to very slow synchronization. In that case you
should define the paths as specifically as possible, in order to speed up
the synchronization process.
</ul>
<!-- -->
</body></html>
|