Home > Storage > PowerScale (Isilon) > Industry Solutions and Verticals > Electronic Design Automation > Synthetic EDA Workloads for At-Scale Storage Benchmarking > Running an Android build job
When the local mirror is ready, you can run Android build to a single node.
Syntax: mkdir <path of work dir>
#mkdir -p /mnt/aosp-build-1
#cd /mnt/aosp-build-1
Syntax: repo init -u <path of local mirror>/platform/manifest.git --depth=1
#repo init -u /mnt/aosp-mirror/platform/manifest.git --depth=1
Syntax: repo sync -j<number of cores> - specify how many cores to use.
#repo sync -j24
#lunch aosp_arm-eng
The lunch command will show all available options for Android build images. You can also input options with the launch command. aosp_arm-eng is used to build engineering image for the arm processor.
m will use all cores
m -j<number of cores> - specify the number of cores to use for the AOSP build
#m -j24
Alternatively run Android build using a script. (You can copy and paste the sample script run_aosp.sh from the Appendix in this document or use any script language preferred to run AOSP build.)
Important: Verify that there are no errors. Try to run the AOSP build on all nodes to check for any configuration errors during an actual build. Make sure that there are no errors during the Android build. Troubleshoot and/or install any missing packages until the job completes successfully.