px4dev b80575fcff Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board. ... This is a first cut; it builds one firmware for each of FMU and IO.		2013-02-23 22:00:58 -08:00
..
firmware.mk	Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board.	2013-02-23 22:00:58 -08:00
gnu-arm-eabi.mk	Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board.	2013-02-23 22:00:58 -08:00
px4fmu.mk	Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board.	2013-02-23 22:00:58 -08:00
px4fmu_default.mk	Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board.	2013-02-23 22:00:58 -08:00
px4io.mk	Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board.	2013-02-23 22:00:58 -08:00
px4io_default.mk	Break up the firmware build into a 'make export' phase for NuttX on a per-board basis, and then a separate per-config phase that allows us to avoid re-building NuttX all the time, and ship more than one firmware config for a given board.	2013-02-23 22:00:58 -08:00