tinyusb.git/examples/make.mk, branch 0.6.0

house keeping

2020-03-26T15:04:24Z

makefile clean up

2020-03-25T07:06:51Z

allow board to define CROSS_COMPILE (default to arm gcc)

Merge branch 'master' into develop

2020-03-24T05:16:15Z

Merge pull request #194 from cr1901/msp430f5529

2020-03-24T04:57:20Z

[WIP] MSP430 Support

per review

2020-03-23T16:22:52Z

- remove -Wno-error=lto-type-mismatch - change back to unsigned int

remove -Wnested-externs since many driver does this including CMSIS_5

2020-03-23T15:52:59Z

Merge branch 'master' into cr1901-msp430f5529

2020-03-22T10:19:57Z

move -flto to board.mk

2019-11-20T09:06:40Z

current board that doesn work with flto is spresense and mimxrt10xx (due to xip image_vector_table is optimized out).

adding support for NXP rt1064 evk board, boad test led + sw8 work.

2019-11-20T08:30:39Z

LTO is temporary disabled

examples: make: specify CROSS_COMPILE for fomu

2019-11-13T17:26:00Z

When BOARD=fomu, use the riscv cross-compiler. Otherwise, use the default arm compiler. This can be overridden by passing CROSS_COMIPLE on the command line. Note that there are now three common risc-v prefixes: - riscv32-unknown-elf- : Common for users who compile their own - riscv64-unknown-elf- : Upstream multiarch toolchain from SiFive - riscv-none-embed- : xPack embedded version of SiFive toolchain Here we assume users are using the `riscv-none-embed-` toolchain from xPack, because it appears to be growing more common. Additionally, there is much confusion surrounding `riscv64-unknown-elf-`, which actually includes both 32- and 64-bit runtimes and can generate software for both. Signed-off-by: Sean Cross