How does one deal with the following sort of library conflicts?
I want the IDE to use all the ESP32 versions of the libraries.
So is there anyway to force Arduino IDE to use the correct version from the correct location of any given library?
Multiple libraries were found for "WiFi.h"
Used: C:\Users\greg\Documents\Arduino\libraries\WiFi
Not used: C:\Users\greg\Documents\Arduino\hardware\expressif\esp32\libraries\WiFiESP32
Not used: C:\Program Files (x86)\Arduino\libraries\WiFi
Multiple libraries were found for "SPI.h"
Used: C:\Users\greg\Documents\Arduino\hardware\expressif\esp32\libraries\SPI
Not used: C:\Users\greg\Documents\Arduino\libraries\SPI
Glad you got it working! I already had the following typed out so I'm posting it anyway:
I can't reproduce the examples issue using Arduino IDE 1.8.3. Which version of the Arduino IDE are you using?
It's easy enough to open examples using File > Open or just double clicking the .ino file if it's associated with the Arduino IDE. If C:\Users\greg\Documents\Arduino\hardware\expressif\esp32\libraries\WiFi\examples is not a convenient location you could save them somewhere else.
As for focing the IDE to use the right version, you could do this:
Yes, I installed specifically to look into this issue. I don't own an ESP32 and I've been waiting for the first release of the Arduino core to really start looking into it rather than trying to work with beta software. I'm really surprised they haven't managed a release yet. I'd think that Espressif would make it a priority.
What I notice in Arduino IDE 1.8.2 or 1.8.3 is that when you have a library installed in the sketchbook with the same name as a library bundled with the hardware package, the one in the hardware package shows up in the "Examples for ESP32 Dev Module" section of the File > Examples menu and the one from the sketchbook shows up in the "Examples from Custom Libraries" section. This is not the behavior you described but it could be considered a bug because if you open one of those examples and compile it the library included with the hardware package is used rather than the library that the example is a part of and that example may not be compatible with the other library.
1.8.3 only has minor changes from 1.8.2. 1.8.2 had a serious bug in the Linux installation script that prompted the release of a minor bugfix version, 1.8.3. People using other operating systems probably won't see a huge difference with 1.8.3 but you also shouldn't encounter any new bugs and it's certainly a good idea to try the latest version when you're encountering undesirable behavior to see if it was already fixed.