I got this in the output window when building the app I'm working on:
Quote:


Per request, I am using Trend Micro Maximum Security.  The board I was building was an "ESP32 Wrover Module".  I don't think however it's anything to do with the virus checker, and the suggested action does nothing useful.  The story is as follows:

I successfully built for the Wrover module many times over the last several months without trouble.  I wanted to try the same app on an M5STAMP Pico.  I installed the Arduino support for the M5STAMP using the Arduino IDE, basically the M5Stack boards definitions and some examples.  I compiled and successfully ran both the LED and the WiFiScan examples for the M5STAMP in the Arduino IDE.  I loaded the WiFiScan example into VS/VM and got lots of errors compiling the WiFi library.  I turned on "includes via Gcc", and it mostly compiled, but choked at a reference to the IPv6Address type in the WiFi library: no error previously in the Arduino IDE.  It seems the M5STAMP is using its own WiFi library, but it should still compile OK in VS/VM if it does so in the Arduino IDE, right?

This is the interesting bit.  Back to my app.  I re-select the ESP32 Wrover Module after cleaning the solution, and now all I get is this:

Quote:


Further, when I go back to the Arduino IDE, WiFiScan now also chokes on IPv6Address. Finally, after removing the M5Stack board definitions, my app builds for the Wrover module.  I am able to build for the M5STAMP ok using the ESP32 Pico Kit board setting, but several questions remain.   Why does the M5STACK board definition affect the other board definitions in VM but not IDE? Why does VM not originally compile the WiFiScan sketch, when the IDE does? I realize that there is probably something amiss in the M5Stack stuff, but it also seems VM is doing something weird also.

Is there a simple explanation of what is happening here?  

Regards,
Jed

Tim,
Sorry, I'd deleted the M5Stack boards defs before I posted.  I have re-installed and emailed you the output.  I used a small example this time, but same result, except it still compiles on IDE; I'm assuming that's an issue with the M5Stack package.

Jed

Tim,
That seems to have been the problem.  It was pretty painless to upgrade to the new ESP32 core, thankfully, but I do now have an annoying flicker on my LEDs that wasn't there before...

I rather think the problem was because the M5Stack has it's own core which conflicted with the older ESP32 package.  Certainly, the WiFi issue was because it was had a later version in the package than the version I'd cloned to my solution.  Not sure why they did that; the "standard" ESP32 package includes 5 or 6 M5 variants already, but not the M5Stamp.  You would think it would be possible to somehow add the M5STAMP variant (and 6 or 7 others) to the espressif package, since they are all ESP32s.  I'm obviously not an expert on that , so I suppose I'd better shut up.

Thanks once more for your help.  Best regards,
Jed

Yes they changed a few things. Hopefully for better