Hello, having AtmelStudio support in VisualMicro is just great!

However I do experience a problem with Tennsy 3.0.

On compile errors I can not see the line numbers the error occured at. Also the lines do not get marked in AtmelStudio.

Example:

\bin\arm-none-eabi-g++ -c -g -Os -fno-exceptions -ffunction-sections -fdata-sections -Wall -mcpu=cortex-m4 -MMD -DUSB_VID=null -DUSB_PID=null -DARDUINO=105 -felide-constructors -std=gnu++0x nsy3"  -o y3\telemetry_convert.cpp.o"  y3\telemetry_convert.cpp"  -DF_CPU=96000000 -DUSB_SERIAL -DLAYOUT_US_ENGLISH -DVISUALMICRO_COMPILER_VER=1  -mthumb -nostdlib -D__MK20DX128__  -fno-rtti
telemetry_convert.ino : 'error_here' does not name a type
telemetry_convert.ino : 'error_here' does not name a type
telemetry_convert.ino : : In function 'void sendValue(uint8_t, uint16_t, uint32_t)':
telemetry_convert.ino : 'sendByte' was not declared in this scope

If I enter the same command into my cmd shell the line numbers are displayed just fine. It seems as if AtmelStudio or VisualMicro strips them.


System used:
VisualMicro 1309.11
Arduino 1.0.5 + Teensyduino latest (Version 1.16)
AtmelStudio 6.1.2730 SP 2
Created a project for Teensy 3.0. Inserted a syntax error.

Any advice?   

Thank you

Sorry for the delay. You should be able to double click many of the errors which will take you to the error line.

Because we allow drill down via double click the error reporting needs more work (which will hopefully be in the next release)

fyi

If you run the raw avr command outside of Atmel or Vs you will see that the std. output points to line numbers in the cpp files of the temporary build folder. This is why we can't allow them to be displayed without re-formatting. Users end up opening the temp copy which will subsequently be overwritten during the next compile process.

Aside from pointing to the source in the temp folder the line numbers also relate to the source in the .cpp created by combining all of the .ino files of the project. This means that both the line numbers and the locations are wrong when looking at the std output and is the reason why vm has to work so hard to reformat errors into usable locations.

Hopefully the double click drill down into error will help a bit but we certainly want to improve this

other refs: http://www.visualmicro.com/page/Teensy-for-Microsoft-Visual-Studio.aspx

Error are fixed along with Teensy intellisense in this pre release https://visualmicro.codeplex.com/releases/view/117112