From 5a959aa47b6fa79534bd5e2b14897507f846b4fc Mon Sep 17 00:00:00 2001 From: Wonchul Lee Date: Tue, 3 Mar 2015 19:26:33 +0900 Subject: [PATCH] validate:docs: Rename gst-validate-launch to gst-validate-launcher https://bugzilla.gnome.org/show_bug.cgi?id=745510 --- validate/docs/validate/command-line-tools.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/validate/docs/validate/command-line-tools.xml b/validate/docs/validate/command-line-tools.xml index 14a30f3406..33c08bed68 100644 --- a/validate/docs/validate/command-line-tools.xml +++ b/validate/docs/validate/command-line-tools.xml @@ -206,7 +206,7 @@ The first time you launch the testsuite, you will need to make sure that the media samples are downloaded. To do so and launch the testsuite you can simply do: - gst-validate-launch validate --sync + gst-validate-launcher validate --sync This will only launch the GstValidate tests and not other application that might be supported @@ -215,7 +215,7 @@ Launching the default testsuite will open/close many windows, you might want to mute it so you can keep using your computer: - gst-validate-launch validate --sync --mute + gst-validate-launcher validate --sync --mute @@ -244,7 +244,7 @@ testsuite_folder/ You should generate the .media_infos files. To generate them for local files, you can use: - gst-validate-launch --medias-paths /path/to/sample_files/ --generate-media-info + gst-validate-launcher --medias-paths /path/to/sample_files/ --generate-media-info For remote streams, you should use gst-validate-media-check-&GST_API_VERSION;. For an http stream you can for example do: gst-validate-media-check-&GST_API_VERSION; http://someonlinestream.com/thestream --output-file /path/to/testsuite_folder/sample_files/thestream.stream_info