From: SirAnthony Date: Fri, 21 Mar 2014 04:21:50 +0000 (+0500) Subject: Merge pull request #2 from ValveSoftware/master X-Git-Url: https://git.notmuchmail.org/git?a=commitdiff_plain;h=9d3f2cdff2c0bb07f341eb8bfc7e52b8086e764f;hp=995901601c88a5d297908de36b13798036c4e829;p=vogl Merge pull request #2 from ValveSoftware/master Merge upstream --- diff --git a/README.md b/README.md index 53b0f28..363e063 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,7 @@ You should now have something like the following in your temp directory: or - vogl/vogl_build/bin/vogleditor64 ; and then open the trace file... + vogl/vogl_build/bin/vogleditor64 /tmp/vogltrace.glxspheres64.2014_01_20-16_19_34.bin ## Directory structure ## diff --git a/qtcreator/qtcreator.md b/qtcreator/qtcreator.md index 0e19829..6f70aca 100644 --- a/qtcreator/qtcreator.md +++ b/qtcreator/qtcreator.md @@ -51,3 +51,19 @@ You should now be able to click in bottom left "Type to locate" control (or hit Note that you can use the "--usemake" flag with mkvolg.sh if you don't want to use Ninja. If you do this, remove the "3>&1 1>&2 2>&3" redirections also. + +### Launching and Debugging projects ### + +The default 'Run configuration' called "VoglProj" that QtCreator adds will not be associated with any binary and therefore cannot be executed. The directions below show how to launch the 64-bit vogleditor. + +* Within the tab, switch to the "Run" settings + * Under "Run", "Run configuration:" click "Add", select "Custom Executable" + * Click "Rename..." and customize this run configuration with an appropriate name (eg, "vogleditor64") + * For the Executable:, enter: %{buildDir}/../vogl_build/bin/vogleditor64 + * For the Arguments:, you may optionally enter a path to a trace file + * Run in terminal does not need to be enabled for vogleditor, but is useful (required?) for other binaries + +* Hit [F5] to start debugging + +This approach allows you to configure mutliple run configurations that (for example) each launch the vogleditor64 with a different trace file as a parameter, or you can have another configuration that launches vogleditor32, or voglreplay64 with parameters to debug why a replay or trim is not working properly. +