Before, the configuration info would be shown again when running a
recursive make call, or when make restarted after regenerating the
dependencies file. Now, it only shows the info the first time.
Closes: #46
In commit 90e3c9ad (Fix upload in case of parallelized make), some
dependencies were shuffled to (I assume) prevent the reset from
happening before or at the same time as the upload when running a
parallel make. However, this introduced two problems:
- The upload and raw_upload became effectively the same, and both of
them did a reset (even though raw_upload should do the upload without
a reset).
- The reset target does not depend on $(TARGET_HEX) or verify_size, so
in a parallel make the reset is executed before / at the same time as
the actual compilation (since the reset doesn't seem to be needed for
at least the Arduino Uno, apparently avrdude handles this, this
probably wasn't noticed by anyone).
Because we can't force a specific ordering of dependencies in parallel
make and because adding dependencies to the reset target doesn't seem
appropriate (you should be able to do a "make reset" without needing to
compile everything first), this commit changes the uploading to call
$(MAKE) again to do the actual upload.
The current approach ensures that:
- raw_upload does a compile, size check and upload and upload does the
same plus a reset.
- A reset is not done if the compilation fails or the size check fails.
- verify_size is called only once.
When there are none (and no .cpp files either), the build would stall
trying to cat all the .d files together (which would result in cat
getting no arguments and thus waiting for input on stdin).
When there are multiple .ino and/or .pde files, the build could
technically work out, the Arduino IDE concatenates all .ino / .pde files
together and compiles them as a single compile unit, so unless we
implement that as well, it's better to just error out.
Before, it would only look in .ino files. If you had no .ino file but
only a .pde file, this would cause the build to hang, since grep would
be waiting for input on its stdin.
This corrects the behaviour of ard-parse-boards --boards , which would
fail if the path to boards.txt on the system didn't match the value
which was hardcoded.