GCC

Additional files:

Teensyduino produces additional files, which are useful if you want to dig more in to the internals or for optimizing.

In principle this should be possible with any of the build systems. Teensyduino creates an .LST and a .SYM file in the build directory.

There is nothing that can't be improved - the generated .SYM file is a bit confusing because the tool nm is not used. But we can easily change that:

Example for Teensy 4:

1. Add a line to boards.txt teensy40.build.command.nm=arm-none-eabi-gcc-nm
2. Add a line to platform.txt recipe.hooks.postbuild.4.pattern="{compiler.path}stdout_redirect" "{build.path}/{build.project_name}.symnm" "{compiler.path}{build.toolchain}{build.command.nm}" -n -S --defined-only -C "{build.path}/{build.project_name}.elf"

Now when we do a new build, an additional .symnm file is created, which is clearer and sorted -- and therefore easier to read.