Tool/software: TI C/C++ Compiler
What is the #include search path order for the TI ARM compiler (or the assembler and the linker, for that matter) when multiple --include_path (or -l) options are passed on the command line? ( --search_path for the linker.)
For example, take the following invocation:
ti-cgt-arm_16.9.4.LTS/bin/armcl --include_path="PathA" --include_path="PathB" file.c
Where file.c includes:
#include <file.def>
Some experimenting suggests that the options passed first have priority over the ones passed later. That is, in the previous invocation PathA will first be searched for file.def, and only if such a file is not present, will PathB be searched. (In other words, if files named file.def are present in both PathA and PathB, it is the one in PathA that will be used.)
Is this reliably the case?
Is this behavior guaranteed for future releases of the TI ARM tools?
Sections 2.5.2 and 2.5.2.1 of spnu151q do not specify this detail. (Nor does section 4.5.1, 8.4.11, or 8.4.18 of spnu118t.)
--thx
(Note, I am aware that when using the "" version, e.g. #include "file.def", first priority in the search path will be given to files in the same directory as the file which has the #include directive.)