In [GCC PR 104342](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104342)
we can see that, if checking out a non-release compiler (e.g. GCC
14.0.1), having `-gnata` and `-fcallgraph-info=su` will cause a crash
(in stm32 code, anyway).
`-gnata` is used when Build is Debug.
This patch amends the Project Wizard so you can specify `CALLGRAPHS=Disabled`.
* scripts/project_wizard.py (Build_Checks_Type): renamed to
Disabled_Or_Enabled_Type.
(Build_Checks): now Disabled_Or_Enabled_Type.
(Callgraphs): new, checks external CALLGRAPHS, default Enabled. Used
to decide whether to include -fcallgraph-info=su even if Target
isn't riscv32-unknown-elf.
to fix loading project in VSCode extension and avoid
> error: cannot set configuration attribute "Target" after it was referenced
See details in GPR issue #166.
* Switch to GNAT FSF 12 support
* GNAT FSF 12 in GitHub CI
* Update README.md
* Remove run-time dependency build script that is not compatible with GNAT FSF
This script is also not needed as all the BSPs are included in GNAT FSF.
startup-gen is a tool that generates crt0 and linker script from a
device configuration (CPU name, memory layout). The tool only works for
ZFP run-times right now.
This patch also switches the HiFive1 support to use startup-gen.
* Add support for NeoPixel and similar LED strips
* Rename MicroBit.IOs.LEDs to MicroBit.IOs.NeoPixel
As suggested on #302.
* Regenerate projects after addition of NeoPixel middleware
This patch makes style checks and warning as error switches controllable
with a scenario variable: ADL_BUILD_CHECKS (disabled by default).
With this we can enforce style checks on all contributions by enabling
ADL_BUILD_CHECKS in testsuite runs and CI builds.
On the other hand the checks are disabled by default which means it is
easier and more friendly to play with the library and the examples.
Part of #271
