| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Fix #128
|
|
Fix #131
|
|
Allow target specific optimization levels/debug flags
|
|
Changing the optimization level from -Os to something else breaks the
SoftwareSerial library. This patch allow optimization flags to be set on a
per target basis.
|
|
|
|
|
|
User-defined or calculated bootloader parent directory
|
|
relative paths as defined in boards.txt e.g. "atmega"
Also added [USER] to ARDUINO_SKETCHBOOK detection
Fixes #126
|
|
|
|
Don't append port details to avrdude for usbtiny
|
|
When using ICSP programmers e.g. usbasp, you can burn sketches directly
to the chip without having to burn a bootloader, however you do need to
set fuses e.g. if you're changing speed/BOD.
Updated help text to include "make set_fuses" and also changed
"make burn_bootloader" help text which wasn't entirely accurate.
Fix #141
|
|
Fix 138
|
|
Adjust path to avrdude/avrdude.conf for MPIDE in Linux.
|
|
|
|
This way we don't assume the make file is 'Makefile' and it will
work even if it is named as 'makefile' or 'makefile-uno'
Fix #130
|
|
Fix #135
|
|
|
|
* Added build step for assembly files in CORE
* Removed duplicate flags from AS build step
|
|
|
|
rationale:
http://unix.stackexchange.com/questions/65803/why-is-printf-better-than-echo
fix #129
|
|
Fix #120
|
|
Code to burn fuses is moved from ispload target to this new target, so
that fuses are burned only once when needed.
Fix #85
|
|
Arduino IDE also reads this from boards.txt file
Fix #125
|
|
Fix #124
|
|
When usbasp is used as programmer, there is no need to specify the port
to avrdude.
Fix #123
|
|
This is just a minor bug fix release
|
|
No change in functionality
|
|
This is needed in Mega boards, because of a bug in Mega bootloader. See
https://github.com/sudar/Arduino-Makefile/issues/114#issuecomment-25011005
for detailed explanation.
Fix #114
|
|
|
|
|
|
Fix #119
|
|
Fix #74
|
|
If these executables are not overridden in the child makefile, then the
default values are not set properly in the master makefile.
This complicates the solution for #119 :(
This reverts commit 66eec82a3af8ee5aa16e28230346e4a1f166da2b.
|
|
Lot of changes went it for this release and the code is stable enough
for 1.0.0
|
|
This is helpful for #119 which will add support for colorgcc
|
|
After #118, we have a separate target (help) to list all available
targets. Having this list in a single place is better, since we don't
have to make changes in multiple places when things change.
|
|
No code or functionality change
|
|
dapicester-help
|
|
Should close Issue #60
|
|
|
|
Add detailed instructions for using alternative cores
Fix #60
|
|
Should close Issue #60
|
|
Till not it is not possible to build with Arduino core, without using a
.ino or .pde file. This commit removes that restriction.
However, the user has to explicitly include Arduino header files.
Fix #105
|
|
Because of the way the autodetect code works, if no .ino/.pde file is
present, then the makefile hangs
|
|
Silence output from the many mkdir calls.
|
|
Both `ARDMK_DIR` and `ARDMK_PATH` needs to be set differently based on
whether the makefile is installed through a package or git checkout.
Refer to #111 to find out why it is needed.
|
|
The show_config_variable macro is available in Common.mk file. So invoke
it for ARDMK_DIR only after Common.mk file is included.
Fix #111
|
|
In 5ed507cf43e048f0a6a527c97ea6ed2e8cdb451f as part of #98,
[`show_config_variable` was duplicated in Arduino.mk file](https://github.com/sudar/Arduino-Makefile/pull/98#commitcomment-3561542)
But it was later found that `ARDMK_DIR` is still not getting printed
(issue #111). This commit therefore removes the duplicated macro
definition.
|
|
If `ARDMK_DIR` is not defined, then it is assumed to be the directory
where `Arduino.mk` or `chipKIT.mk` is present.
Since this assumption is made, `ARDMK_DIR` will always be set, whether
the user has explicitly set it or not. Therefore checking whether
`ARDMK_DIR` is not set is unnecessary. This commit removes these
unnecessary checks.
|
