Lines Matching refs:version

4 map.txt files. These files are [linker version scripts] with comments that are
10 [linker version scripts]: https://www.gnu.org/software/gnulib/manual/html_node/LD-Version-Scripts.h…
14 A linker version script defines at least one alphanumeric "version" definition,
32 Comments on the same line as either a version definition or a symbol name have
38 `MY_API_R` version and `api_baz` is exposed with the `MY_API_S` version. No
42 When generating NDK API stubs from this version script, the stub library for R
46 Note that, with few exceptions (see "Special version names" below), the name of
47 the version has no inherent meaning.
49 These map files can (and should) also be used as version scripts for building
57 ## Special version names
61 naming schemes is equivalent to marking the version with the `platform-only`
66 Comments on the same line as a version definition or a symbol name are
72 Indicates that the version or symbol is to be exposed in the APEX stubs rather
78 Indicates that the version or symbol is first introduced in the "future" API
84 Indicates the version in which an API was first introduced. For example,
86 API level 21. This tag can be applied to either a version definition or an
87 individual symbol. If applied to a version, all symbols contained in the version
89 set for the version, if both are defined.
122 Indicates that the version or symbol is to be exposed in the LL-NDK stubs rather
128 Indicates that the version or symbol is public in the implementation library but
146 Behaves similarly to `introduced` but defines the first version that the stub