[michael.s]

splendid…thanks

[michael.s]

Thanks,

 

that was it. I will evaluate how the different intellisense systems will do. the thing I like about the VA Bar is the “Go” button, where you can quickly jump to the definitions or implemtations of code items your cursor is at. Anyway, thanks a lot…

[michael.s]

I know this is an old thread, but I just hit the same problem and i found a different solution. so for anybody in the same situation:

If you go to the propreties of your project (not the GDB-properties!!!, normal Visual Studion properties) you open the NMAKE configuration property. you see three lines starting with the ‘build command line’ and it is filled with the Visual-GDB-commandline like: “$(VISUALGDB_DIR)\VisualGDB.exe” /build “$(ProjectPath)” ….

click on the line and see, that there is a pop-up triangle on the right side of the edit field. click it and click ‘edit…’. An extra window opens with one line – the

“$(VISUALGDB_DIR)\VisualGDB.exe” /build “$(ProjectPath)”…

line. you can now add a line before (pre-build execution) or after it (post-build execution). Do the same to the other lines, if you wish.

I used it for SubWCRev.exe to automatically build myself a version.h from the SVN repository at pre-build-time and it works like a charm.

cheers

[michael.s]

Hi Tristan (Fishermen;),

we just had the same problem and the reason and solution is quiet simple. VisualGDB offer you 2 toolchains to download for the raspberry…the older one seems to be for the standard Wheezy image from the raspberry pi homepage. the second and newer toolchain seems to be for the new ‘Jessie’-upgrade.

so you either use the old toolchain or you upgrade your pi to Jessie (that’s what we did)…here is how it’s done

http://raspberrypi.stackexchange.com/questions/27858/upgrade-to-raspbian-jessie

the upgrade took us a couple of hours!!! but in the end it compiled just fine with the newer toolchain. I hope that works for you too..

Michael

[Author]

Posts