The problem is that it's not fully and/or clearly described in documentation.
In addition, there's a small caveat or trick to get it working: Internal Updates.
For the general setup, Oracle has pointed me out to the following good references:
To begin, install Oracle Solaris Studio on every local coding and remote build hosts.
On the coding nodes, hosts with a GUI, update all plug-ins, notably the C/C++ one.
This will assure the correct configuration and operation of remote build hosts.
You should see something similar to the following:
 | |
| C/C++ plug-in updates (Internal Updates) |
To finish preparations, also make sure that:
- The same login account is consistently used.
This includes uid and gid values as well.
- SSH (preferably) or NFS is properly configured.
Note that NFS is important to the mixed mode only.
The remote build configuration is set up in the Build Hosts Manage dialog box.
It's invoked by the main menu File | Create Remote C/C++ Project | Manage Hosts...
To change a remote build host properties,
click the Properties... button.
To add a remote build host,
click the Add.. button:
- Type in the host FQDN in Hostname and click the Next > button.
Then enter the Login/User and Password information.
Consider ticking Remember Password checkbox.
Click the OK button.
- After a while the Tool Collections should be correctly detected.
Select the appropriate project files access (synchronization) method.
Again, this depends on the desired remote development mode.
Finally, click the Finish button to conclude the host addition.
- There's an additional step if the synchronization is System Level File Sharing.
Use the Path Mapper... button to map paths to the sources' central location.
