[quote="Deva_Rishi, post:19, topic:1440350"]
s
Hi I am getting the verbose output . I assume it is writing it to a file somewhere . I was trying to find the file without success .
Hi I can see it being a lot slower when I have wifi include files
Verbose output is not written to file. You can copy and paste from the output to a text editor to make analysis easier.
If you want somebody here to have a look at it you can copy and paste the output here (using code tags).
If you post the complete code we can compile it as well and let you know how long a compilation takes on our system(s).
Hi I am not sure if my compiler is using cashed files on the second run . Is there any way to check ? I am not sure if there is an option choice i must select ?
On a Windows system you can find the cache in
C:\Users\yourUsername\AppData\Local\arduino
There are two directories; you can delete both.
Next compile.
After a first compile you should see the directories recreated and the cache of your project is in a subdirectory.
Note timestamps; compile again and check which timestamps (e.g. for libraries) have changed. It should only be the ino.cpp file.
Something you could compare with:
I'm running Win 11 on a 15 year old MacBook (8GB RAM / i5 2.9 GHz) and using IDE 1.8.13. Compiling the code from https://randomnerdtutorials.com/esp32-access-point-ap-web-server/ took 1 minute 29 seconds. May have had some build files cached from a previous ESP32 build. Compiling a second time with no changes took 17 seconds
I have a dual boot machine and find that compilation on Linux (Ubuntu) is about twice as fast. I rarely use the Windows 11 side.
EDIT:
Found a post I made a while ago. Difference is more then twice.
Your virus scanner/firewall may also slow down the compilation...
It might be helpful to compare a completely empty sketch with one adding just #include <WiFi.h> and WiFi.begin("", "")
If you enable verbose output, you should see the names of several stages, along with unnamed first and last stages, named "prepare" and "final" below. These are the times for a moderately complex sketch on a low-end quad-core with dual boot. (I patched the back-end cli to print these timings.)
| Linux | Win11 | |||
|---|---|---|---|---|
| clean | cached | clean | cached | |
| prepare | 0.612 | 0.867 | 2.880 | 6.045 |
| detecting libraries | 34.633 | 4.947 | 133.938 | 19.014 |
| function prototypes | 0.760 | 0.754 | 2.689 | 2.689 |
| compiling sketch | 5.035 | 1.339 | 12.976 | 3.189 |
| compiling libraries | 21.529 | 0.140 | 62.677 | 0.397 |
| compiling core | 4.569 | 0.153 | 17.925 | 3.759 |
| linking | 5.393 | 5.074 | 6.933 | 6.804 |
| final | 0.501 | 0.494 | 1.245 | 1.153 |
| -------- | -------- | -------- | -------- | |
| Total, seconds | 73.032 | 13.768 | 241.265 | 43.05 |
In the verbose output, it will say "Using previously compiled file" for both library sources and any separate source files in your sketch. The .ino is always converted to .ino.cpp and recompiled. For the core, it will say "Using precompiled core". That's how the times go way down in "cached" columns in the table above.