ardupilot/Tools/ardupilotwaf
Gustavo Jose de Sousa 1b6a87d8b4 waf: toolchain: clang: use waf to find toolchain path
The find_realexec_path function was used for finding the toolchain path mostly
because of two reasons:

 1) We couldn't really use CXX or CC variables because the user could set those
 from the OS's environment and Waf wouldn't look for the executable file in
 that case.

 2) Our CI configuration sets up symlinks for ccache and find_realexec_path
 works around that issue.

The bad side about using find_realexec_path() is that, besides working aroung
symlinks, it does the same thing that is done by Waf. This patch removes the
dependency for such a function by addressing each of the reasons above stated:

 1) We create a local copy of os.environ and, if there's a variable with the
 same name we are using, we remove it from the local copy.

 2) As done before, we are looking for the cross ar program instead of gcc
 program, since that is not used for ccache symlinks.
2016-03-23 17:11:02 -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: load compilers tools in toolchain tool 2016-03-23 17:11:02 -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: implement --upload option 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: toolchain: clang: use waf to find toolchain path 2016-03-23 17:11:02 -03:00