Lines Matching full:files
7 written to describe your C and C++ source files to the Android
37 don't need to list header files or explicit dependencies between
38 generated files in your Android.mk. The NDK build system will
43 without having to touch your Android.mk files.
45 Note that the syntax is *very* close to the one used in Android.mk files
55 "hello JNI" example, i.e. the files under:
90 It is used to locate source files in the development tree. In this example,
101 control files are parsed in a single GNU Make execution context where
115 This is to support Android.mk files that originate from the
121 files that will be built and assembled into a module. Note that you should
122 not list header and included files here, because the build system will
123 compute dependencies automatically for you; just list the source files
126 Note that the default extension for C++ source files is '.cpp'. It is
140 Android.mk files that you can look at.
277 will only look for files in sources/*/Android.mk
316 The module name determines the name of generated files, e.g.
319 name (e.g. <foo>) in your NDK build files (either Android.mk
323 This is a list of source files that will be built for your module.
324 Only list the files that will be passed to a compiler, since the
327 Note that source files names are all relative to LOCAL_PATH and
333 NOTE: Always use Unix-style forward slashes (/) in build files.
338 the file extension of C++ source files. The default is '.cpp'
360 C *and* C++ source files.
369 useful data files used during debugging.
372 to C source files, not C++ ones. This has been corrected to
382 C++ source files *only*. They will appear after the LOCAL_CFLAGS
427 if you want to force the generation of the module's object files in
448 NEON instructions in Assembly files.
457 Alternatively, you can also specify that only specific source files
