- This topic has 3 replies, 2 voices, and was last updated 9 years ago by
.
-
Posts
-
I have been evaluating VGDB for a control project on a Raspberry Pi and am about to commence serious development. First, I will be taking the opportunity to update the Pi software, which implies changing the c++ version to 4.9.
As I compile on a Win7 machine, then run on the Pi, I shall need to update the toolchain on the PC.
Is this as easy as just replacing the X-compiler or are there settings to be made in VGDB (which? how?)? In the extreme, would it be better to completely remove VGDB from the PC and re-install it?
Any advice appreciated.
Hi,
You can simply replace your cross-compiler (or install it into a different directory and choose it from the wizard) and VisualGDB will show it as an option in the wizard. You can also retarget your existing projects to a different compiler via VisualGDB Project Properties -> Toolchain Settings.
Note that you can also download our pre-built Jessie image for Raspberry Pi that includes a newer GCC: http://gnutoolchains.com/raspberry/jessie/
Thanks, Bazis. That worked fine.
However, I now see that it appears to still load headers for intellisense from the old toolchain location, even though all projects are pointed to the new one. That gives me cause for concern if I delete the old (now redundant) toolchain from the PC. Is there a way to remove reference to the old toolchain from vgdb and make the new one the default?
A separate question, please: how does one change the default compiler flags eg to have ‘-std=c++11’ appear automatically without having to add it each time?
And another: frequently during testing, I want to examine the program output after execution has finished. The ‘Output’ tab always defaults to ‘VisualGDB Custom Shortcuts Output’. Can the default be set to ‘Visual GDB Program Output’ or the setting be remembered from one debug run to the next? Just a minor annoyance.
Regards.
Hi,
Normally when you change something on the Makefile Settings page and click “Apply” VisualGDB should retest the settings and update IntelliSense. Did this not happen when you changed the toolchain? Does it retest correctly when you change, let’s say, CFLAGS?
We’ll add an option to select the language directly in the wizard in the next version of VisualGDB. We will also see if we can make the Program Output to be the default output after debugging.
- You must be logged in to reply to this topic.