-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hooks for early upload prep & cleanup #317
Comments
Hi Paul, |
Must confess, I haven't worked with the builder code, nor with Google Go language... so probably no PR from me anytime soon. If I had to do this one my own, I'd just put an ugly kludge into the Java code. |
No worries, I will remember this request as soon as we touch the builder (or the cli) again 😉 |
I'd like to request special hooks to run recipes intended to minimize the wait time for uploading.
A hook similar to recipe.hooks.sketch.postbuild.NUMBER.pattern is needed, but only run if the build is for Upload. If the user clicked Verify, this recipe should not be run. The idea is to begin the process of a board rebooting as early as possible (but after the user's sketch it known to compile without errors), to allow time for USB enumeration and driver initialization while the build process continues.
Another build error hook would probably also be needed. If building any library, the core lib, or linking fails, the error hook would run a recipe which quits bootloader mode and causes the selected board to reboot to whatever code was previously programmed.
For the common case of relatively small sketches on native USB boards like MKR & Micro (and Teensy), the time for USB enumeration is often the a large chunk total time required to upload. If we could start that early in the build process, users could have a much quicker total upload experience.
The text was updated successfully, but these errors were encountered: