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) Re: Intellisense errors with Marlin + ADK (Read 10500 times)
uiewiuwfeiub
Newbies
*
Offline


Posts: 9
Joined: Nov 27th, 2015
Re: Intellisense errors with Marlin + ADK
Nov 28th, 2015 at 9:48pm
Print Post  
What I mean, it is hard to know if it is successfull or not. Which errors in the "error list" are save to ignore? Which not? Will the built file wreck my 3D printer? No errors and a success message would give me a better feeling.
In C# it is "normal" that an error means "forget the build".
« Last Edit: Dec 1st, 2015 at 11:15pm by Tim@Visual Micro »  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: VM ignores excluded header files
Reply #1 - Nov 29th, 2015 at 12:11am
Print Post  
Hi,

I will try to add more obvious messages but this is what you see in the arduino ide when build succeeds and also in visual micro.

Binary sketch size: 50'902 bytes (used 39% of a 130'048 byte maximum) (6.30 secs)
Minimum Memory Usage: 3059 bytes (19% of a 16384 byte maximum)


It is not possible to have a memory size or sketch size if the build fails.

The build messages are 100% accurate, the intellisense is less accurate.

  
Back to top
IP Logged
 
uiewiuwfeiub
Newbies
*
Offline


Posts: 9
Joined: Nov 27th, 2015
Re: How to know if build was OK
Reply #2 - Nov 29th, 2015 at 10:14am
Print Post  
Thanks for the feedback. I admit, I never used the Arduino IDE.  Embarrassed
  
Back to top
 
IP Logged
 
uiewiuwfeiub
Newbies
*
Offline


Posts: 9
Joined: Nov 27th, 2015
Re: How to know if build was OK
Reply #3 - Nov 29th, 2015 at 10:25am
Print Post  
Since the other thread has been locked, I just want to tell you, that I think your tool is cool but I wait a few months and look into it again then. It spits out too much errors for me. The header file problem is then hopefully solved.
If anyone is interested, I have forked Marlin on Github and added VM solution/projects:
https://github.com/indazoo/Marlin.git

You find the VisualMicro files in the Marlin subfolder.

Hint, Hint, Hint: This project has over 2000 forks (potential customers maybe?)
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: How to know if build was OK
Reply #4 - Nov 29th, 2015 at 12:50pm
Print Post  
Hi,

Your first post was not related to this discussion so I split it into a new thread.

You need to make sure the toolbar is set to release for Marlin which redefines Serial so the default debugger will fail to compile.

After that any "errors" you see must be warnings which you must have turned on? "Visual Micro>Verbose" and "Visual Micro>Show warnings" these are off by default?

If you are seeing intellisense errors and not build errors then please say which arduino ide version you are using because that can affect things. I will look at it sometime to see how it differs from std arduino, you can switch off intellisense error reporting in the "errors windows" if they are confusing.

There are quite a few marlin users already thanks but maybe needs a revisit as the Ide's have changed a lot (both vs and arduino) recently. However it will be through user reports and posting of errors that will speed the work up. Thanks
« Last Edit: Nov 29th, 2015 at 1:30pm by Tim@Visual Micro »  
Back to top
IP Logged
 
uiewiuwfeiub
Newbies
*
Offline


Posts: 9
Joined: Nov 27th, 2015
Re: How to know if build was OK
Reply #5 - Nov 29th, 2015 at 9:09pm
Print Post  
Yes, If you have again an Arduino Newbie tell him that not only to select "Release" but also "x86" instead of x64 for a 32 Bit processor. Shocked
Then, I hope, the following errors are only header-file-wrongly-included_errors. 

Error (active)            #error directive: Uncomment #define AT90USBxx_TEENSYPP_ASSIGNMENTS in fastio.h for this config      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_BRAINWAVE_PRO.h      15
Error (active)            identifier "DOGLCD_CS" is undefined      Marlin      c:\DEV\reprap\Marlin\Marlin\dogm_lcd_implementation.h      136
Error (active)            identifier "DOGLCD_A0" is undefined      Marlin      c:\DEV\reprap\Marlin\Marlin\dogm_lcd_implementation.h      136
Error (active)            #error directive: Oops!  Make sure you have 'Teensy++ 2.0' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_5DPRINT.h      8
Error (active)            #error directive: Oops!  Make sure you have 'Brainwave' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_BRAINWAVE.h      9
Error (active)            #error directive: Oops!  Make sure you have 'Brainwave Pro' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_BRAINWAVE_PRO.h      9
Error (active)            #error directive: Oops!  Make sure you have 'Sanguino' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_GEN3_MONOLITHIC.h      6
Error (active)            #error directive: Oops!  Make sure you have 'Sanguino' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_GEN3_PLUS.h      6
Error (active)            #error directive: Oops!  Make sure you have 'Sanguino' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_GEN6.h      7
Error (active)            #error directive: Oops!  Make sure you have 'Gen7' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_GEN7_12.h      6
Error (active)            #error directive: Oops!  Make sure you have 'Gen7' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_GEN7_14.h      8
Error (active)            #error directive: Oops!  Make sure you have 'Gen7' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_GEN7_CUSTOM.h      9
Error (active)            #error directive: Oops!  Make sure you have 'Minitronics' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_MINITRONICS.h      6
Error (active)            #error directive: Oops!  Make sure you have 'Sanguino' selected from the 'Tools -> Boards' menu. (Final OMCA board)      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_OMCA.h      33
Error (active)            #error directive: Oops!  Make sure you have 'SanguinoA' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_OMCA_A.h      32
Error (active)            #error directive: Oops!  Make sure you have 'Teensy++ 2.0' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_PRINTRBOARD.h      9
Error (active)            #error directive: Oops!  Make sure you have 'Sanguino' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_SANGUINOLOLU_11.h      6
Error (active)            #error directive: Oops!  Make sure you have 'Teensy++ 2.0' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_SAV_MKI.h      9
Error (active)            #error directive: Oops!  Make sure you have 'Sethi 3D' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_SETHI.h      6
Error (active)            #error directive: Oops!  Make sure you have 'Teensy++ 2.0' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_TEENSY2.h      47
Error (active)            #error directive: Uncomment #define AT90USBxx_TEENSYPP_ASSIGNMENTS in fastio.h for this config      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_TEENSY2.h      51
Error (active)            #error directive: Oops!  Make sure you have 'Teensy++ 2.0' selected from the 'Tools -> Boards' menu.      Marlin      c:\DEV\reprap\Marlin\Marlin\pins_TEENSYLU.h      9
Error (active)            #error directive: HEATER_0_PIN not defined for this board.      Marlin      c:\DEV\reprap\Marlin\Marlin\SanityCheck.h      326
Error (active)            cannot overload functions distinguished by return type alone      Marlin      c:\DEV\reprap\Marlin\Marlin\ultralcd_implementation_hitachi_HD44780.h      414
Error (active)            expected a type specifier      Marlin      c:\DEV\reprap\Marlin\Marlin\ultralcd_implementation_hitachi_HD44780.h      741
Error (active)            expected a type specifier      Marlin      c:\DEV\reprap\Marlin\Marlin\ultralcd_implementation_hitachi_HD44780.h      754
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: How to know if build was OK
Reply #6 - Nov 29th, 2015 at 9:32pm
Print Post  
Thanks the x64/32 bit issue has only become a problem in VS2015. I need to spend a little time to see if the x64 config can also be updated.

I can't really comment on the intellisense errors without knowing which board and which arduino ide version is used for reprap. Can you also send a verbose compiler output to info[at]visualmicro.com? 

Thanks
« Last Edit: Nov 29th, 2015 at 9:33pm by Tim@Visual Micro »  
Back to top
IP Logged
 
uiewiuwfeiub
Newbies
*
Offline


Posts: 9
Joined: Nov 27th, 2015
Re: How to know if build was OK
Reply #7 - Nov 30th, 2015 at 8:55am
Print Post  
You should also tell him (this unknown dude) about the possibility to select 
"Build + Intellisense"
"Build Only"
"Intellisense Only"
For the "Error List" window in Visual Studio.
Then all errors go away. Some warnings will still appear though. The warnings are probably not your business but it would be nice if you can nuke the intellisense errors.

I take back my comment about "waiting a few months" and apologize for the troubles I created.
The build works just fine now.
Case closed for me and thanks a lot. Smiley
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: How to know if build was OK
Reply #8 - Nov 30th, 2015 at 12:36pm
Print Post  
Thanks very much for the feedback.

VS2015 has changed things and the documentation will catch up soon Smiley
  
Back to top
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: How to know if build was OK
Reply #9 - Nov 30th, 2015 at 6:41pm
Print Post  
Thanks for the files.

The compiler warnings you see with Visual Micro are correct. The Arduino Ide is suppressing them with the -w param in the compile but Visual Micro uses the -wall param which shows them all.

Have you switched on "Visual Micro>Compiler Warnings"? If so switch it off and you should see the same output as the arduino ide. You can also switch off  Verbose if you want to more easily see when the build has finished.

As for the intellisense I will look into it. It's using the standard megaADK 2560 so I wouldn't expect to see some/most of those errors.
  
Back to top
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12187
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Intellisense errors with Marlin + ADK
Reply #10 - Dec 1st, 2015 at 11:14pm
Print Post  
I've looked at Marlin and I get many less errors when I use an arduino 1.5.x ide which is what it was designed for.

The intellisense errors you see are because it has a complex set of board name and #defines that need to be set. You haven't given me any info about what you have configured in the code for the marlin, it's very heavily customizable.

I can't spend too long looking at it. I expect if a project can be fully configured with the correct #defines there might still be some errors remaining. Some of which I could resolve but it's impossible with without configuring the project correctly from a source perspective. 

For example I got a lot of errors until I defined which LCD to use. However it needs to know which board type to use so many other errors will appear and confuse the issue.
« Last Edit: Dec 1st, 2015 at 11:15pm by Tim@Visual Micro »  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint