diff options
author | DaveHodder67 <dave.hodder@focusrite.com> | 2015-07-06 21:54:35 +0100 |
---|---|---|
committer | DaveHodder67 <dave.hodder@focusrite.com> | 2015-07-06 21:54:35 +0100 |
commit | 5937e719a815fdcd5b0181d62f16dfa3c5f4c8a3 (patch) | |
tree | 869b10ccde11fc6f778dcf55f4d48f921ccc89c1 | |
parent | 80a27faec1221dc501c08f0527b821bdba403bdf (diff) | |
download | launchpad-polymaker-5937e719a815fdcd5b0181d62f16dfa3c5f4c8a3.tar.gz launchpad-polymaker-5937e719a815fdcd5b0181d62f16dfa3c5f4c8a3.zip |
debugging tips
-rw-r--r-- | README.md | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -95,6 +95,15 @@ Instead, you're going to have to do things the old fashioned way - by blinking L | |||
95 | 95 | ||
96 | If do you want to debug interactively (and of course you do), you can use the simple command-line simulator located in the `/tools` directory. It is compiled and ran as part of the build process, so it serves as a very basic test of your app before it is baked into a sysex dump. If you want to test particular button presses or MIDI messages, just modify it to send those messages to your app, and debug away. Yes, it's rudimental - wiring it up to the device over MIDI for interactive testing would be fab! | 96 | If do you want to debug interactively (and of course you do), you can use the simple command-line simulator located in the `/tools` directory. It is compiled and ran as part of the build process, so it serves as a very basic test of your app before it is baked into a sysex dump. If you want to test particular button presses or MIDI messages, just modify it to send those messages to your app, and debug away. Yes, it's rudimental - wiring it up to the device over MIDI for interactive testing would be fab! |
97 | 97 | ||
98 | To debug the simulator interactively in Eclipse: | ||
99 | |||
100 | 1. Click the down arrow next to the little "bug" icon in the toolbar | ||
101 | 2. Choose "Debug configurations..." | ||
102 | 3. Right click "C/C++ Application" and choose "New...: | ||
103 | 4. Under "C/C++ Application" click Browse... and locate the simulator binary at `/vagrant/build/simulator` | ||
104 | 5. Hit "Debug"! | ||
105 | |||
106 | |||
98 | # Vagrant tips | 107 | # Vagrant tips |
99 | When you're done developing, simply type `vagrant suspend` to halt your VM without destroying it - this will make `vagrant up` a lot quicker next time. If you're really finished, `vagrant destroy` will completely remove the VM from your system (but not any of your code). | 108 | When you're done developing, simply type `vagrant suspend` to halt your VM without destroying it - this will make `vagrant up` a lot quicker next time. If you're really finished, `vagrant destroy` will completely remove the VM from your system (but not any of your code). |
100 | 109 | ||