Gustavo Jose de Sousa e6fa2d54e8 waf: px4: build firmware ... Copy the program library to the place where PX4Firmware CMake build will look for and trigger the firmware build. There isn't really a real output defined for px4_copy_lib because Waf would complain about multiple tasks having same output when building multiple programs. After the firmware build, copy it to the correct place (from program group and name perspective) and add git hashes. Since the place where the library is placed is shared by different target programs, we need to synchronize the firmware build, that's why the use of _firmware_semaphorish_tasks. That variable is set as a list because of the upcoming upload task.		2016-03-14 11:54:31 -03:00
..
px4/cmake/configs	waf: px4: add initial implementation	2016-03-14 11:54:31 -03:00
__init__.py	waf: add waf support	2015-12-03 07:54:30 +11:00
ardupilotwaf.py	waf: ardupilotwaf: add option --upload	2016-03-14 11:54:31 -03:00
boards.py	waf: boards: define PX4 boards	2016-03-14 11:54:31 -03:00
cmake.py	waf: cmake: live output!	2016-03-14 11:54:30 -03:00
gbenchmark.py	waf: gbenchmark: use cmake tool	2016-02-22 15:36:48 -03:00
git_submodule.py	waf: git_submodule: support recursive submodules	2016-03-14 11:54:31 -03:00
gtest.py	waf: gtest: disable for PX4 boards	2016-03-14 11:54:31 -03:00
mavgen.py	waf: use git_submodule tool through GIT_SUBMODULES variable	2016-02-06 10:25:08 -02:00
px4.py	waf: px4: build firmware	2016-03-14 11:54:31 -03:00
static_linking.py	waf: add static_linking tool	2016-01-11 16:31:59 -02:00
toolchain.py	waf: add toolchain tool for cross-compiling	2016-01-11 16:31:59 -02:00