Previous: Connection settings, Up: Setup the remote servers
The last configuration part is to define the path translations between your local host and the remote server.
The remote paths definition will allow GPS to translate your locally loaded project (e.g. 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.
All your project's dependencies must then reside in a path that is defined
here. Note that you can retrieve those paths by using gnat list
-v -Pyour_project
.
To add a new path, click on the +
button, and enter the corresponding
local and remote paths.
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 Connection settings.) Clicking
on Apply
will apply your connection configuration and allow you
to browse the remote host to select the remote paths.
Four kind of paths synchronisation can be set for each defined path:
None
: no synchronisation is required from GPS, the paths
are shared using an OS mechanism like NFS.
Always
: source path of your project. They are kept
synchronised by GPS before and after every remote action.
Once to local
/Once to remote
: project's
dependencies. They are synchronized once when a remote project is
loaded or when a local project is set remote. They can be still
manually synchronized using the Remote View (See The remote view.)
The way those paths need to be configured depend on your network architecture.