Advanced modification of environment

Note: If you have not setup your environment, please do so. You can use the setup guide as a reference.

As the contributing page states, the project is made modular to ease customization. This page will describe the ways you can customize the script to your liking. If you are looking for ways of integrating this project into some other project, please refer to the integrate wiki page instead.

More on the modular design can be found on the integrate wiki page.

Multiple configurations

---

Because you have to specify the configuration files at the command line it enables you to create different configuration files and switch between them as you like. This feature makes it easier to distribute the software with different configuration files instead of having to edit said files. All you have to remember if you change file names is to point to the right files in the configuration files.

Custom modifications

---

While the defaults changes a lot of things in your environment you might want to control what the scripts modifies. All you have to do is edit the right file. The key-value pairs in conf/ramdisk-modifications.txt will affect the ramdisk.img file, while conf/system-modifications.txt will affect the system.img file.

Configuration file layout

---

setup-tools.conf: Used by setup-tools.sh

TestName-avd.conf: Used by install-avds.sh, referred by setup-env.conf

TestName2-avd.conf: Used by install-avds.sh, referred by setup-env.conf

modify-env.conf: Used by modify-env.sh

sysimgs.txt: Used by modify-ramdisk-image.sh and modify-system-img.sh, referred by modify-env.conf

ramdisk-modifications.txt: Used by modify-ramdisk-img.sh, referred by modify-env.conf

system-modifications.txt: Used by modify-system-img.sh, referred by modify-env.conf