Home | History | Annotate | Download | only in core

Lines Matching refs:Are

21 # If NDK_TRACE is enabled then calls to the library functions are
83 # Rationale: Checks that all variables listed in $1 are defined, or abort the
128 # Note that we want mixed paths, which are supported by our toolchain binaries.
153 # The following declarations are used to manage the list of modules
166 # Also, LOCAL_XXXX values defined for a module are recorded in XXXX, e.g.:
172 # Some of these are created by build scripts like BUILD_STATIC_LIBRARY:
179 # Note that some modules are never installed (e.g. static libraries).
183 # The list of LOCAL_XXXX variables that are recorded for each module definition
184 # These are documented by docs/ANDROID-MK.TXT. Exception is LOCAL_MODULE
210 # The following are generated by the build scripts themselves
396 # NOTE: this function must not modify the existing dependency order when new depends are added.
700 # Tags are processed by a toolchain-specific function (e.g. TARGET-compute-cflags)
702 # These are currently stored as:
1154 $(call __ndk_info,Are you sure your NDK_MODULE_PATH variable is properly defined ?)\