dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity
4,993 Commits 514 Branches 136 Tags 234 MiB
Commit Graph

213 Commits

Author SHA1 Message Date
px4dev d24599931a APP -> MODULE 
remove as many duplicate slashes, etc. as seems practical
 2013-02-23 22:01:00 -08:00
px4dev 8d7621079a Checkpoint: application framework makefile done 2013-02-23 22:00:59 -08:00
px4dev 3494039d90 Get a bit fancier with the builtin app specifications, so that we can generate them from apps as well as the config. 2013-02-23 22:00:59 -08:00
px4dev 50739c1843 platform -> board 2013-02-23 22:00:59 -08:00
px4dev abe48bd714 Auto-generate builtin command prototypes. 
Tidy up path configuration, etc.
 2013-02-23 22:00:59 -08:00
px4dev a7a1cc4625 Add support for per-config ROMFS generation. 2013-02-23 22:00:59 -08:00
px4dev 963621c1f3 Rename makefiles to help categorise them. 2013-02-23 22:00:59 -08:00
px4dev 8440e4f709 Simplify the PLATFORM/CONFIG handling a little. 2013-02-23 22:00:59 -08:00
px4dev e9f2197bfa Move upload functionality out into a separate makefile. 2013-02-23 22:00:59 -08:00
px4dev e692ccc44e Move more functionality into firmware.mk. Now we build the px4 bundles in a way that will let external builders generate them too. 
Pass the platform define into the firmware builder.
 2013-02-23 22:00:59 -08:00
px4dev 0140457d03 Minor fixes to the toolchain definitions. 2013-02-23 22:00:58 -08:00
px4dev d2d9800c2e Recover commits lost in the previous merge. Syllableise PX4_BASE like its peers. 2013-02-23 22:00:58 -08:00
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