| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
POSIX shells treat an unquoted [abcd] as a pattern bracket expression
and apply it for filename expansion. This kicks in and causes
troubles in the space_pad_to function when it's called to pad prefix
tags like '[AUTODETECT]', because the argument holding such a tag is
passed to a shell unquoted. The result is funny output when the
directory containing the Makefile also contains any files or
directories, whose name is a single upper-case character that can be
found in any prefix tags:
$ touch A B C D
$ make
-------------------------
Arduino.mk Configuration:
- A C D CURRENT_OS = LINUX
- [USER] ARDUINO_DIR = /home/szeder/src/arduino/arduino-1.8.1
- [USER] ARDMK_DIR = /home/szeder/src/arduino/Arduino-Makefile
- A C D ARDUINO_VERSION = 181
- A D ARCHITECTURE = avr
- A D ARDMK_VENDOR = arduino
- A D ARDUINO_SKETCHBOOK =
<snip>
Prevent this by quoting space_pad_to's parameter when passing it to a
shell.
|
|
impact performance we should track when the issue is fixed upstream to remove the flag again (see links from Issue #486)
Enabled colourised diagnostics from avr-gcc
We forgot to increase ARDMK_VERSION for the 1.6.0 release
|
|
|
|
Considering the number of project files spread in different locations
when developing an Arduino project, proper use of tags can be difficult;
resolving beyond local functions.
I've added automatic generation of a tags file, which includes:
* Standard ctags source in project dir (.c, .cpp, .h)
* Arduino source in project dir (.ide, .pde)
* Arduino core based on detected project core from Arduino install.
* Included Arduino libraries from user library folder.
As a Vim user I find this hugely useful and think it would be a useful
addtion for others. Target has been added as `make tags`.
|
|
|
|
Remove use of tilde in documentation as ~ doesn't work, use $(HOME) instead
|
|
over ssh
|
|
|
|
|
|
|
|
Do not include the Arduino header when generating assembly for .cpp
files with generate_assembly. This was likely a copy-paste error.
|
|
|
|
|
|
|
|
build.core and
build.variant
Fixes Issue #461
|
|
IDE prior to 1.6.10
doesn't support LTO or plugins. Fixes Issue #456
So essentially LTO support will only be enabled with avr-gcc 4.9.2 which comes with 1.6.10 or later
and Debian, Ubuntu etc; not 4.8.1 which comes with IDE 1.6.9 and a few earlier versions.
Tested with:
* 1.6.8 (avr-gcc 4.8.1 which doesn't support LTO so uses avr-ar and doesn't set LTO flags)
* 1.6.12 (avr-gcc 4.9.2 which supports LTO so uses avr-gcc-ar and sets LTO flags)
* 1.0.5 with Debian avr-gcc 4.9.2 (supports LTO so uses avr-gcc-ar and sets LTO flags)
|
|
|
|
|
|
Updated HISTORY.md with latest commits
|
|
Updated to reflect the Linux changes for Arduino 1.6.5
Updated to reflect the information (Linux portion) from the guide. Removed the URL to the blog.
|
|
|
|
|
|
|
|
BOOTLOADER_FILE in 1.5+
Now we just check for BOOTLOADER_FILE being non-empty on both versions.
Fixes issue #402
|
|
e.g. attiny44-20, thanks to Atmel for the sample chip!
|
|
|
|
|
|
|
|
$ARCHITECTURE is probably safe as that's usually called $ARCH.
Fixes issue #386.
Need to decide if this is going to upset too many user's who have already
started using $VENDOR - and who uses tcsh? ;-)
|
|
not just on Windows - fixes issue #381
Code around this area probably needs a tidy up at some point.
|
|
|
|
With this fix the `TARGET` variable is set correctly when the project directory
(or its path) contains spaces. So in this case:
/Users/Joe/Dropbox (Personal)/example project
`TARGET` will be set to `example_project` instead of `Dropbox example project`
(like it was before this fix).
|
|
|
|
|
|
Needed to fix the new wiring_pulse.S in IDE 1.6.5 which
also has a wiring_pulse.c source file.
Mostly rebased @peplin's PR #266, so should allow us
to support newer chipKIT builds too.
|
|
|
|
|
|
|
|
Fix #359
|
|
|
|
Fixes #352
|
|
|
|
|
|
|
|
I found that the previous reset code did not work for Leonardo or Micro, nor did any reset code anywhere on the internet.
An examination of the Arduino IDE source code (and the JNI code behind its serial implementation) shows that it holds RTS high and DTR low when doing the 1200 baud open/close. And it turns out that's exactly what's needed!
|
|
|
