Lines Matching refs:build

31 * On a developer preview build, dynamic linker warnings will also show up
98 above. (Use --hash-style=both if you want to build code that uses this
117 Some apps have bad DT_NEEDED entries (usually absolute paths on the build
233 *Resolution*: remove the extra steps from your build that strip section
300 Even worse, some build systems have bugs that cause them to insert
301 DT_NEEDED entries that point to a file on the build host, something that
310 [C:\Users\build\Android\ci\jni\libBroken.so]
316 device. There are broken third-party toolchains/build systems that use
317 a path on a build host instead of the SONAME.
329 or a misconfiguration in your build system. A missing SONAME may lead
345 configured your build system to generate incorrect SONAME entries (using
356 *Resolution*: build your code with an NDK target API level that matches your
451 rather than at build time. This lets us use the same `libc.so` on all