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
Normal Topic no good errormessage, because of compiler -o nul (Read 1673 times)
Bummibaer
Newbies
*
Offline


Posts: 3
Joined: Sep 14th, 2016
no good errormessage, because of compiler -o nul
Feb 22nd, 2017 at 11:09am
Print Post  
Hi,
I got messages about not defined variables.
The reason was, I removed an include-file by mistake.
But because compiler gives no output ( >nul), I don't
know in the first time about the missing file.In VS it was still shown.
It would be nice, to get compiler output in verbose mode too.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12188
Location: United Kingdom
Joined: Apr 10th, 2010
Re: no good errormessage, because of compiler -o nul
Reply #1 - Feb 22nd, 2017 at 12:55pm
Print Post  
Thanks, I will try to replicate and test so that I understand.

I am not entirely clear what this means:-

Quote:
to get compiler output in verbose mode too.


Surely if a header is missing you should see a clear message with verbose On and Off? So I am trying to understand what is missing from verbose or what difference verbose should show over normal?

Finally, if you hit confusion in this area before visual micro has been updated the "vMicro>Compiler>Deep Search" does not produce "-o null". In this case all required libraries must be #included in the .ino file.
  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint