
## Listing Installed Files in AOSP with make dump-files
In the AOSP build system, the <mark>make dump-files</mark> command lets you see the list of files that will be installed for the current target product.  
The output goes to <mark>stdout</mark> (not a separate file) and lists relative paths based on `PRODUCT_OUT`.
### 1. Run dump-files
Initialize the build environment, then run the following command.
```sh
{
    "title": "Run make dump-files"
}
---
$ source build/envsetup.sh
$ lunch <your_target>
//[!code highlight]
$ make dump-files
Target files for <product>-<variant> (<product>.mk):
system/app/Settings/Settings.apk
system/lib/libc.so
system/bin/sh
...
Successfully dumped product target file list.
```
### 2. Redirect Output to a File
Since the output can be large, redirecting it to a file makes it easier to analyze.
```sh
{
    "title": "Save output to a file"
}
---
//[!code highlight]
$ make dump-files > dump-files.txt
$ wc -l dump-files.txt
1234 dump-files.txt
```
### 3. Compare Before and After Configuration Changes
By saving the output before and after a configuration change, you can use `diff` to immediately see which files were added or removed.
```sh
{
    "title": "Diff between two dump-files"
}
---
# Save before configuration change
$ make dump-files > dump-files.before.txt

# (Apply configuration changes, then rebuild)

# Save after configuration change
$ make dump-files > dump-files.after.txt

//[!code highlight]
$ diff -u dump-files.before.txt dump-files.after.txt
--- dump-files.before.txt
+++ dump-files.after.txt
@@ ... @@
+system/app/NewApp/NewApp.apk
+system/lib/libnewfeature.so
-system/app/OldApp/OldApp.apk
```
This is useful for verifying that only the intended files are included after changing product configuration (e.g., `PRODUCT_PACKAGES`).

How to use make dump-files in AOSP to list all files that will be installed into the product output directory.