GalaxyNexusI9250Build » History » Revision 5
Revision 4 (Loic Dachary, 10/22/2016 10:04 PM) → Revision 5/7 (Wolfgang Wiedmeyer, 09/11/2017 07:29 PM)
h1. Galaxy Nexus (I9250) Build This page explains how to build Replicant for the Galaxy Nexus (I9250). h2. Prerequisites Before building, you must make sure that: * You have installed the build dependencies: [[BuildDependenciesInstallation]] * You have downloaded Replicant 6.0 4.2 sources: [[ReplicantSourceCode]] * Your sources are up to date: [[ReplicantSourceCode#DownloadingUpdating-the-source-code|Downloading/Updating [[ReplicantSourceCode#DownloadingUpdating-the-source-from-the-repos|Downloading/Updating the source from the repos]] * Your terminal is running in the directory where the sources were downloaded h2. Warning *Do not build as root, always build as user.* See the [[BuildTips|build tips]] if you are facing issues. h2. Building All of Setup the following build commands need to be run in the source tree root folder. First, the toolchain needs to be built: environment: <pre> ./vendor/replicant/build-toolchain </pre> *If you have executed any of the commands below and you want to run the toolchain build again, you will need to open a new shell.* Then, prepare the shell environment for the Replicant build: <pre> . source build/envsetup.sh lunch replicant_maguro-userdebug export ANDROID_JAVA_HOME=$JAVA_HOME </pre> Now you can start Start the build: <pre> parallel_tasks=$(echo "$(grep 'processor' /proc/cpuinfo | wc -l ) + 1" | bc) make -j$parallel_tasks bacon </pre> The @-jn@ -jn argument indicates is to indicate the number of parallel tasks during the build. You can remove it from the command line to have only one task at a time. @$parallel_tasks@ holds an optimized number of parallel tasks for your hardware. You may want to reduce this number if e.g. the computer runs out of RAM during the build. Finally, sign the resulting images: <pre> ./vendor/replicant/sign-build maguro </pre> The first time you run the script, it With fast hardware, best results will ask you a few questions that are needed to generate the necessary signing keys. come with @-j9@, @-j16@ and @-j32@. h2. Output files The produced files are located at: * built target images: @out/dist/maguro/@ @out/target/product/maguro/@ * built host tools: @out/host/linux-x86/bin/@