Hello !

Compilation is also very slow on my side. I saved the verbose output and attached. Can you help? Thank you!

---

Hi,

The thread was answered so I moved this question to a new one.

The quick post on this page does not show the attachments option. Cilick the Reply button to add attachments.

Thank you

Please find the verbose output attached to my first post.

Thanks for the logs.

If you disable the Serial Debugger is the compilation considerably faster?

If not would it be possible to send us the entire solution via email so we can investigate this further?

Hi

We are looking into this issue. It is certainly attempting to scan too much code in the core during compilation.

We will come back with some questions on Monday.

Regards

This should be resolved in the latest release (21.11.08-07), which is available from the top of the board below:
https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

Hello,

Thank you. Build time is now reduced to ~12 secs. I hope one day it will be ~1 sec ;) , but it's OK for now :)

Thx again!
Balázs

Good to hear that.

Please open the project and click build. After the build complete click build again.

Then send us the output. It will be useful to check that the output is correct.

12 secs sounds too long for a cached build of a small/medium sized project.

Thanks

I did as you proposed, please find the verbose output attached. What is strange is that I can't switch debug to off. whenever I click to "off", I stays "Serial".

---

Thanks, "Auto Debugging" is on by default. You can use the configuration names on the toolbar to switch between "Release" and "Debug".

Got it; I switched to "Release", then my 2nd build took ~10 secs. Did you find anything by my log analysis?

Great, It looked good. 10 secs is probably okay, it depends on the speed of the pc disk/cpu,virus checkers etc.

Some toolchains do have event hooks defined. The hooks normally run .exe's, we can't cache what they do. For example the output shows that the board you are using runs "recipe.hooks.linking.prelink" events.

The "deep search for libraries" system has the highest cost in your build. Switching it off means that the .ino code must have an #include for at least one .h file of each library that the project needs to use. With deep search "on", the output shows the libraries that are used. Without deep search the #includes in the .ino need to include the same libraries. The last consideration, without deep search, if the code uses "types" before they are defined (not in earlier code) then the auto generated prototypes might be inserted in an incorrect position.

Thank you for the detailed explanation. In my example I realized that it can be compiled without deep search, so every "type" is defined at the right place. By switching deep search off, I spared even more compilation time, so now it is ~5 secs that makes rapid development possible.