diff options
| author | José Fonseca <jfonseca@vmware.com> | 2013-04-12 10:30:21 +0100 |
|---|---|---|
| committer | José Fonseca <jfonseca@vmware.com> | 2013-04-12 10:50:11 +0100 |
| commit | 9d42c85063ac13f574ffd00b8be31bbd39f29a70 (patch) | |
| tree | ce7a386606c7cdcd2821d57aa4d28e9579775b8c /README.markdown | |
| parent | ff6dad3ca0f52fb91b5035843df7da79126291e1 (diff) | |
Cleanup README formatting.
Diffstat (limited to 'README.markdown')
| -rw-r--r-- | README.markdown | 30 |
1 files changed, 16 insertions, 14 deletions
diff --git a/README.markdown b/README.markdown index 4bf809e9..7545982e 100644 --- a/README.markdown +++ b/README.markdown @@ -418,10 +418,9 @@ Or on Windows: python scripts\retracediff.py --retrace \path\to\glretrace.exe --ref-env TRACE_LIBGL=\path\to\reference\opengl32.dll application.trace -[](http://githalytics.com/apitrace/apitrace) - Advanced GUI usage ================== + qapitrace has rudimentary support for replaying traces on a remote target device. This can be useful, for example, when developing for an embedded system. The primary GUI will run on the local host, while any @@ -429,22 +428,22 @@ replays will be performed on the target device. In order to target a remote device, use the command-line: - qapitrace --remote-target <HOST> <trace-file> - + qapitrace --remote-target <HOST> <trace-file> + In order for this to work, the following must be available in the system configuration: - + 1. It must be possible for the current user to initiate an ssh session that has access to the target's window system. The command to be exectuted by qapitrace will be: - - ssh <HOST> glretrace + + ssh <HOST> glretrace For example, if the target device is using the X window system, one can test whether an ssh session has access to the target X server with: - ssh <HOST> xdpyinfo + ssh <HOST> xdpyinfo If this command fails with something like "cannot open display" then the user will have to configure the target to set the DISPLAY @@ -455,18 +454,21 @@ system configuration: this must be configured on the host side so that ssh can be initiated without a username. - For example, if you normally connect with "ssh user@192.168.0.2" + For example, if you normally connect with `ssh user@192.168.0.2` you could configure ~/.ssh/config on the host with a block such as: - Host target - HostName 192.168.0.2 - User user + Host target + HostName 192.168.0.2 + User user - And after this you should be able to connect with "ssh target" so - that you can also use "qapitrace --remote-target target". + And after this you should be able to connect with `ssh target` so + that you can also use `qapitrace --remote-target target`. 2. The target host must have a functional glretrace binary available 3. The target host must have access to <trace-file> at the same path in the filesystem as the <trace-file> path on the host system being passed to the qapitrace command line. + + +[](http://githalytics.com/apitrace/apitrace) |