Lines Matching refs:used

49 These map files can (and should) also be used as version scripts for building
68 interpreted by the stub generator. Multiple space-delimited tags may be used on
76 May be used in combination with `llndk` if the symbol is exposed to both APEX
82 level. This is an arbitrarily high API level used to define APIs that have not
86 but **will not be included in the NDK**. `future` should generally not be used,
105 Code names can (and typically should) be used when defining new APIs. This
107 that release. For example, `introduced=S` can be used to define APIs added in S.
108 Any code name known to the build system can be used. For a list of versions
124 Note: The architecture-specific tags should, in general, not be used. These are
132 than the NDK. May be used in combination with `apex` if the symbol is exposed to
155 should be used for APIs exposed by an APEX to the platform or another APEX.
157 May be used in combination with `llndk` if the symbol is exposed to both APEX
167 sure that the old platform which used the symbol has reached EOL and thus is no
169 control over how APIs are used, we are in a much more controllable environment
177 tag may be used.
198 This tag is not commonly needed and is only used to hide symbol versioning