| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
The intermediate files used for build (.o, .a ...) are still
in subfolders to avoid conflicts.
Fix #3807
|
|
|
|
|
|
The number of hyphens in this URL has apparently changed.
|
|
This uses the gnu11 standard, which is C11 with GNU extensions.
Previously, gnu89 was being used, which is pretty ancient by now. C99
brings some important improvements, some of which were already available
and used even without this option. C11 is more recent and brings more
minor improvements. Most notable feature is the static_assert statement,
allowing checking invariants at compiletime using the full C
expressions.
|
|
This uses the gnu++11 standard, which is C++11 with GNU extensions.
C++11 should be full compatible with the previously used C++98
standards, so all pre-existing sketches should continue to work.
|
|
This does not change anything, it just makes the defaults explicit.
|
|
|
|
|
|
Signed-off-by: Arnav Gupta <championswimmer@gmail.com>
|
|
* Moving Upload options from "File" menu to "Sketch" menu as those
are sketch actions more than file actions.
Signed-off-by: Arnav Gupta <championswimmer@gmail.com>
|
|
|
|
|
|
Provided a default value for compiler.warning_flags
Releasing avr core 1.6.5
|
|
|
|
|
|
https://github.com/arduino/Arduino/commit/61592d78fa71c023e4f1577f7e2b6bada2661a13#commitcomment-10668365
|
|
Updated toolchains: linux statically compiled, added gcc lto plugin (disabled)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This allow to define specific recipes for every platform
but keeps backward compatibility.
See #2614
|
|
using generic term 'output', because for samx32,
output is .bin format and not .hex
Signed-off-by: Arnav Gupta <championswimmer@gmail.com>
|
|
|
|
Previously, when verbose uploads were enabled, avrdude was run with four
-v options, causing it to dump all raw bytes exchanged with the
bootloader. This floods the console so much that meaningful output
mostly disappears.
Most users probably want to enable verbose mode just to see what avrdude
command is ran. Furthermore, users that benefit from the raw bytes
dumped are perfectly capable of either running avrdude manually, or
modifying platform.txt. Given that, running avrdude with just one -v
should be plenty.
This fixes #891.
|
|
The following empty stubs has been replaced by the gcc
flag -fno-threadsafe-static:
int __cxa_guard_acquire(__guard *);
void __cxa_guard_release (__guard *);
void __cxa_guard_abort (__guard *);
The following empty stubs has been moved into their specific
module abi.cpp:
void __cxa_pure_virtual(void) __attribute ((noreturn));
void __cxa_deleted_virtual(void) __attribute ((noreturn));
Fix #107
|
|
|
|
worked out.
For more info:
https://groups.google.com/a/arduino.cc/d/msg/developers/21G5w2HbUOg/NRMW6c9OIFUJ
|
|
this fix is just a workaround
|
|
warning http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59396
|
|
|
|
|
|
Previously, this relied on an (ugly, avr-specific) magic default for the
compiler.path variable, set by the IDE. This allowed the IDE to fall
back to a system-wide toolchain when no bundled toolchain was found (by
making compiler.path empty).
However,
- this only worked for avr, not sam,
- this worked only for gcc, a system-wide avrdude would break on the
avrdude.conf path in platform.txt, and
This would mean that automatic system-wide fallback didn't work in all
situations, so you'd still have to modify platform.txt (or create
platform.local.txt). Since doing that explictly is the most reliable
way, this commit removes the partial-working ability to do this
automatically.
Note that the code to automatically set compiler.path is still kept
around, in case third-party hardware still relies on this. At some
point, this code should be removed, but for now it just shows a warning
message.
|
|
These make it easier for a user to add extra compiler flags in a
platform.local.txt file.
|
|
|
|
- Newer avr-gcc doesn't use -assembler-with-cpp, but
uses -x assembler-with-cpp. This works with older compilers as well.
|
|
"runtime.hardware.path" now contains the path to the hardware folder
of the currently selected board and "runtime.platform.path" the path
to the specific platform.
This should fix #1176 and #1761.
|
|
|
|
|
|
See #1422.
|
|
See #1422.
|
|
platform.txt
|
|
Fixes #1457
|
