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 Compiler warnings. (Read 7072 times)
n
Junior Member
**
Offline


Posts: 52
Joined: Mar 29th, 2016
Compiler warnings.
Nov 8th, 2016 at 5:27am
Print Post  
Hi,

I have recently updated my VS2015 to update 3 and since then I get dozens of repeating compiler warnings of the form:

WARNING: Missing unmatched library header: lwip/opt.h
WARNING: Missing unmatched library header: lwip/udp.h
WARNING: Missing unmatched library header: lwip/igmp.h
WARNING: Missing unmatched library header: include/UdpContext.h
WARNING: Missing unmatched library header: user_interface.h
WARNING: Missing unmatched library header: spi_flash.h
.
.
.

The warnings are all referring to system library files - not my own code.

The sketch compiles successfully despite the warnings but I would like to understand and eliminate them. 

The Arduino IDE does not give any warnings and so I guess it is something to do with the VS update.

I have no idea what the warnings mean and, for once, google doesn't seem to be much help. 

Can anybody explain what the issue is here and perhaps tell me how to correct it - or alternatively guide me to a switch in either VS or Visual Micro to suppress them.

Thanks

n



  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12138
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compiler warnings.
Reply #1 - Nov 8th, 2016 at 1:04pm
Print Post  
Hi,

Warnings can be switched off vMicro>Compiler>Warnings

  
Back to top
IP Logged
 
n
Junior Member
**
Offline


Posts: 52
Joined: Mar 29th, 2016
Re: Compiler warnings.
Reply #2 - Nov 8th, 2016 at 7:51pm
Print Post  
Hi Tim - they are off already. 

Do you know where these messages are being generated?

Thanks

n
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12138
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compiler warnings.
Reply #3 - Nov 8th, 2016 at 9:15pm
Print Post  
Visual Micro produces the message if it can't find headers but as far as I can see they only appear if you have compiler>verbose or uploader>verbose enabled.

Do you have either of the verbose settings switched on?

ps: i will probably remove them from future builds. They were more for testing and not errors.
« Last Edit: Nov 8th, 2016 at 9:27pm by Tim@Visual Micro »  
Back to top
IP Logged
 
n
Junior Member
**
Offline


Posts: 52
Joined: Mar 29th, 2016
Re: Compiler warnings.
Reply #4 - Nov 8th, 2016 at 9:30pm
Print Post  
Hi Tim,

Indeed, Upload>Verbose was enabled and the messages disappear when it is disabled. Thanks

I'm still a bit puzzled though - from the above it appears the messages come from the uploader and yet they still appear when I am only compiling and not uploading? 

Also, can you explain what exactly the warning messages mean? What do I need to do to resolve them?

Thanks

n
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12138
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compiler warnings.
Reply #5 - Nov 8th, 2016 at 9:43pm
Print Post  
What about Compiler>Verbose is that switched off?

The messages are from the pre-processing where code attempts to resolve #includes to work out which libraries need to be compiled.

So the messages suggest there are some #includes in the project code that are not found in libraries and also not found in the project.

End of last year and earlier this year arduino intriduced a new more accurate way to find libraries. Visual Micro uses the new design if "compiler>deep search" is enabled but in all cases it still also uses the older system which can find #includes that are unused due to preprocessor defines such as :-

#if defined(foo)
  #include "lib.h"
#endif

If #foo is not defined then the header might still be detected and an attempt made to resolve a library.

So the messages can be ignored and will be removed from future releases.
« Last Edit: Nov 8th, 2016 at 9:43pm by Tim@Visual Micro »  
Back to top
IP Logged
 
n
Junior Member
**
Offline


Posts: 52
Joined: Mar 29th, 2016
Re: Compiler warnings.
Reply #6 - Nov 8th, 2016 at 9:58pm
Print Post  
Hi Tim,

Thanks - I will ignore the messages.

However, just to answer your question about the compiler verbose switch:

1) If neither compiler or uploader are set to verbose then there are no warnings.

2) If only Uploader is set to verbose there are still warning messages even if I am only compiling!

Thanks

n
« Last Edit: Nov 8th, 2016 at 9:59pm by n »  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12138
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Compiler warnings.
Reply #7 - Nov 8th, 2016 at 10:03pm
Print Post  
Thanks
  
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint