Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Hot Topic (More than 8 Replies) Compile errors of core code when activating debug configuration (Read 10145 times)
Marius
Developer
****
Offline


Posts: 204
Location: Centurion RSA
Joined: Sep 7th, 2011
Compile errors of core code when activating debug configuration
Dec 26th, 2014 at 1:11pm
Print Post  
Hi
I get a huge amount of compile errors of core code when I activate the debugger. I am running the latest release software version 1.1412.10 or at least this is what the config shows.

Some of the Errors :

>Build started 2014-12-26 15:00:43.
1>InitializeBuildStatus:
1>  Touching "Debug\udpcomms.unsuccessfulbuild".
1>ClCompile:
1>  wiring_shift.c
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(13): warning C4005: '__AVR_ATmega328p__' : macro redefinition
1>          command-line arguments :  see previous definition of '__AVR_ATmega328p__'
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(14): warning C4005: '__AVR_ATmega328P__' : macro redefinition
1>          command-line arguments :  see previous definition of '__AVR_ATmega328P__'
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(16): warning C4005: 'ARDUINO_MAIN' : macro redefinition
1>          command-line arguments :  see previous definition of 'ARDUINO_MAIN'
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(17): warning C4005: '__AVR__' : macro redefinition
1>          command-line arguments :  see previous definition of '__AVR__'
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(18): warning C4005: '__avr__' : macro redefinition
1>          command-line arguments :  see previous definition of '__avr__'
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(20): warning C4005: '__cplusplus' : macro redefinition
1>          command-line arguments :  see previous definition of '__cplusplus'
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(27): warning C4005: '__asm__' : macro redefinition
1>          c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(22) : see previous definition of '__asm__'
1>c:\users\mariusl\documents\arduino\udpcomms\visual micro\.udpcomms.vsarduino.h(40): error C2059: syntax error : 'string'
1>c:\arduino_1_5_4\hardware\tools\avr\avr\include\stdlib.h(54): error C2059: syntax error : 'string'
1>c:\arduino_1_5_4\hardware\tools\avr\avr\include\string.h(56): error C2059: syntax error : 'string'
1>c:\arduino_1_5_4\hardware\tools\avr\avr\include\math.h(95): error C2059: syntax error : 'string'
1>c:\arduino_1_5_4\hardware\tools\avr\avr\include\avr\pgmspace.h(106): error C2059: syntax error : 'string'
1>c:\arduino_1_5_4\hardware\tools\avr\avr\include\avr\interrupt.h(110): error C2010: '[' : unexpected in macro formal parameter list
1>c:\arduino_1_5_4\hardware\tools\avr\avr\include\avr\interrupt.h(110): error C2010: ']' : unexpected in macro formal parameter list
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\arduino.h(15): error C2059: syntax error : 'string'
1>c:\arduino_1_5_4\hardware\tools\avr\avr\include\ctype.h(48): error C2059: syntax error : 'string'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(26): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(26): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(27): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(27): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(28): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(28): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(29): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(29): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(30): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(30): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(31): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(31): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(32): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(32): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(33): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(33): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(34): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(34): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(35): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(35): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(36): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(36): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(37): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(37): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(38): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(38): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(39): error C2054: expected '(' to follow 'inline'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(39): error C2085: 'toAscii' : not in formal parameter list
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(40): error C2061: syntax error : identifier 'inline'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(41): error C2054: expected '(' to follow 'inline'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(41): error C2085: 'toUpperCase' : not in formal parameter list
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(46): error C2061: syntax error : identifier 'inline'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(54): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(54): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(56): warning C4013: 'isalpha' undefined; assuming extern returning int
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(62): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(62): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(64): warning C4013: 'isascii' undefined; assuming extern returning int
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(69): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(69): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(71): warning C4013: 'isblank' undefined; assuming extern returning int
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(76): error C2061: syntax error : identifier 'boolean'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(76): error C2059: syntax error : ';'
1>c:\arduino_1_5_4\hardware\arduino\avr\cores\arduino\wcharacter.h(78): warning C4013: 'iscntrl' undefined
  
Back to top
IP Logged
 
Marius
Developer
****
Offline


Posts: 204
Location: Centurion RSA
Joined: Sep 7th, 2011
Re: Compile errors of core code when activating debug configuration
Reply #1 - Dec 26th, 2014 at 1:31pm
Print Post  
I also tried with arduino 1.0.5 and I get the same.


I also noticed that I dont have all the debugger settings that are mention in the documents. Maybe I have something turned off again? although I have not fiddled with the debugger settings for a long time Smiley
  
Back to top
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compile errors of core code when activating debug configuration
Reply #2 - Dec 26th, 2014 at 2:06pm
Print Post  
Hi Marius,

Not sure it's connected to the debugger. The errors are Visual Studio errors when it fails to compile the C++ project. That means that Visual Micro has hit some sort of config error and given up, allowing VS to do what it would normally do for Arduino (not much)

The output you are seeing is also because vs has switched the output window.

Can you please click the list of "output windows" and select the "Micro Build" output window then post or email the output after failed compiled.

Thanks
  
Back to top
IP Logged
 
Marius
Developer
****
Offline


Posts: 204
Location: Centurion RSA
Joined: Sep 7th, 2011
Re: Compile errors of core code when activating debug configuration
Reply #3 - Dec 26th, 2014 at 2:13pm
Print Post  
Ok more trying to sort my issues out. I started a new empty project and compiled for Debug. The debugger tries to load an exe file to execute. It seems like my debugger is not visible.
  
Back to top
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compile errors of core code when activating debug configuration
Reply #4 - Dec 26th, 2014 at 3:05pm
Print Post  
Hi Marius,

That's the same thing. If vs takes over the build it will try to compile an exe then run it

This all suggests that visual micro is either not working at all due to install clash or some other exception is happening such as arduino ide location is wrong in the options.

To prove it is unrelated to debug please try "debug>start without debugging". It should fail in the same way.

Can you click the "Micro Output" window and report what it shows? or does the micro output window not appear in the output windows list?

Thanks
  
Back to top
IP Logged
 
Marius
Developer
****
Offline


Posts: 204
Location: Centurion RSA
Joined: Sep 7th, 2011
Re: Compile errors of core code when activating debug configuration
Reply #5 - Dec 27th, 2014 at 6:17am
Print Post  
If I run the debugger in my release configuration then I get it to work. Apart from being really dumb sometimes, what am I missing here?
  
Back to top
IP Logged
 
Marius
Developer
****
Offline


Posts: 204
Location: Centurion RSA
Joined: Sep 7th, 2011
Re: Compile errors of core code when activating debug configuration
Reply #6 - Dec 27th, 2014 at 6:41am
Print Post  
Hi Tim
Sorry I did not see your post before I replied. The micro build output is not shown and if I start without debugging it still wants the exe file.
  
Back to top
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compile errors of core code when activating debug configuration
Reply #7 - Dec 27th, 2014 at 7:30am
Print Post  
You are never dumb Smiley

One thing that springs to mind is an old and forgotten setting that allows you to force a given configuration to allow VS to handle everything.

Check the tools>options>compiler debug and release fields are empty

Thanks
  
Back to top
IP Logged
 
Marius
Developer
****
Offline


Posts: 204
Location: Centurion RSA
Joined: Sep 7th, 2011
Re: Compile errors of core code when activating debug configuration
Reply #8 - Dec 27th, 2014 at 8:13am
Print Post  
Tim
I am still using VS2010 so I dont have the settings that you are referring to. 
Some other strange behaviour - when I click the "?" to get the explorer, it opens the VM project properties window. Something is drastically wrong with my installation.

What is the correct uninstall procedure to follow. Maybe I should start from scratch with the installation.
  
Back to top
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compile errors of core code when activating debug configuration
Reply #9 - Dec 27th, 2014 at 9:57am
Print Post  
Its an option to have the prop window open

How many projects on solution?

Delete the visuaal micro folder from below the sketch and reopen the ide and project

Thanks
  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint