Lines Matching refs:that

4 map.txt files. These files are [linker version scripts] with comments that are
33 meaning. If you need to add any comments that should not be interpreted by the
46 Note that, with few exceptions (see "Special version names" below), the name of
53 file. Without this, APIs that you have not explicitly exposed will still be
60 Version names that end with `_PRIVATE` or `_PLATFORM` will not be exposed in any
73 Indicates that the version or symbol is to be exposed in the APEX stubs rather
79 Indicates that the version or symbol is first introduced in the "future" API
80 level. This is an arbitrarily high API level used to define APIs that have not
90 `introduced=21` specifies that the API was first added (or first made public) in
105 that release. For example, `introduced=S` can be used to define APIs added in S.
118 tag when generating stubs for that architecture if both are present. If the
120 for architectures that are not named.
123 primarily needed for APIs that were wrongly inconsistently exposed by libc/libm
129 Indicates that the version or symbol is to be exposed in the LL-NDK stubs rather
137 Indicates that the version or symbol is public in the implementation library but
140 clear to the developer that they are up to no good.
142 The typical use for this tag is for exposing an API to the platform that is not
155 Behaves similarly to `introduced` but defines the first version that the stub
173 mistakes that shipped as part of the platform.
176 `ndk_library` Soong module may define a `unversioned_until` property that sets
181 Indicates that the symbol should be [weak] in the stub library.