[GUIDE] Setting Up A Build Environment on OS X 10.9 Mavericks

Hello everyone,

I've come across, and been asked, a lot of questions regarding how to properly setup a build environment on OS X, so I'm going to make this guide on how to setup a build environment on OS X 10.9 Mavericks.

this is only for setting up the build environment, and since most ROMs use different configurations, you will need to refer to your specific ROM for how to initialize their source and build

Setting Up an Android Build Environment on OS X 10.9 Mavericks


A Word To The Wise

Code:

/**
 * if you don't follow my instructions exactly as they are written, several things will happen:
 * 1 - If you don't know what you're doing, it won't work
 * 2 - I won't respond with help, since everything you need IS RIGHT HERE 
 **/

Click to expand...

Click to collapse

What You Will Be Installing:

• XCode 5
• Android SDK (includes ADB and Fastboot)
• repo
• Homebrew
• Many, many packages required for building Android

Click to expand...

Click to collapse

XCode

XCode is roughly a 4 GB download from the AppStore. Once it is downloaded, it will start an installation process, where it will download more software and install XCode on your system. Depending on your hardware, and your internet speeds, this could take a long time.

Apple XCode 5 for OS X 10.9 Mavericks

Or just search for "XCode" in the App Store

Once XCode is downloaded and installed, you can pretty much forget about it. Just don't uninstall it.

Click to expand...

Click to collapse

Java

Java for OS X 2013-005

Click to expand...

Click to collapse

Android SDK

Android SDK​

• Extract the contents of the Android SDK download archive to a new folder and name it android-sdk
• Create a new folder in your HOME directory ( ~/ ) named android [your home directory can be found by opening Finder, and clicking on your username in the column to the left]
• Move the android-sdk folder INTO the android folder you just made in your Home directory ( it will be ~/android/android-sdk )
• Using Finder, navigate to the android/android-sdk/tools folder.
• Double-click the "android" file and go through the installer for Android SDK

Click to expand...

Click to collapse

Homebrew

Code:

ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go/install)"

This will begin the download and installation of Brew.

Depending on your hardware and internet connection, this could take a bit.

Now, we need to run a few commands through Brew, just to make sure everything is installed correctly. Enter the following into the Terminal:

Code:

brew outdated && brew update && brew upgrade && brew doctor

After running brew doctor, you should receive a message saying the follow: Your system is ready to brew.

Now, we can install the packages required to build Android.

Click to expand...

Click to collapse

Required Packages For Compiling Android

Enter the following command into the Terminal:

Code:

brew install git coreutils findutils gnu-sed gnupg pngcrush python

This WILL take a while.

Click to expand...

Click to collapse

Repo

Open Terminal and enter the following:

Code:

mkdir -p ~/.bin

curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo

chmod a+x ~/bin/repo

Click to expand...

Click to collapse

Creating A Case-Sensitive Volume

We need to create a CASE-SENSITIVE image for our development. Android cannot be build on case-insensitive images, so we need to make one.

Enter the following into the Terminal.

Code:

hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 60g -volname "android" -attach ~/Desktop/Android

I have it set to be 60 GB here, but you can increase or decrease the size to whatever you choose, simply change the "60" to any number of GB you want it to be. I generally use 100 GB.

Once the command is done, you will see a new .img on your desktop, called android.sparseimage. This is the volume you just created that will store your source. To mount it, you just simply double-click it.

Click to expand...

Click to collapse

Setting Up bash_profile

Enter the following into Terminal:

Code:

~/.bash_profile

Now copy / paste this into the terminal, so it's in the bash_profile you're creating:

Code:

export PATH=~/bin:$PATH
export PATH=~/android/android-sdk/sdk/platform-tools:$PATH
export PATH=/usr/local/bin:$PATH
export BUILD_MAC_SDK_EXPERIMENTAL=1
export LC_CTYPE=C 
export LANG=C

Save it by pressing Ctrl + X , then Ctrl + Y

Once back at the command line in Terminal, enter the following:

Code:

source ~/.bash_profile

Click to expand...

Click to collapse

Here is a list of commits, organized alphabetically by repository, that you will need to cherry-pick in order to ensure the best compatibility for building on OS X:

If you come across other commits related to building on OS X that I have not listed, PLEASE respond to the thread and mention me. I'll get them added!

build
https://github.com/CyanogenMod/android_build/commit/e04d4ddad4790a5f67d96873890cdc8230f0e18a

openssl / sha1sum errors?
https://github.com/CyanogenMod/android_build/commit/18c1d6d96df97b975b87a2736446c9dfd3ab4169

readink -f errors?
https://github.com/omnirom/android_build/commit/27e819cd6b6c44cbb86a0dc2bd3d735ad5dc09e7

sed/gsed errors that is NOT "sed: RE error: illegal byte sequence"?
https://github.com/omnirom/android_build/commit/24b9c1bfe07d24f7e2a425d9d5aae52fd30f3819

errors with the zip creation?
https://github.com/omnirom/android_build/commit/08c61654feff40eeec04eef40f4970408de1e229

JNI errors in /external/chromium_org ?
external_chromium_org
https://github.com/CyanogenMod/andr...mmit/5130af630390487b37d99941887883647c67f37a

Click to expand...

Click to collapse

fzr-r4 said:

for others using this awesome guide, don't forget to install repo in terminal the following commands before initializing repo

$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ cd ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Click to expand...

Click to collapse

MikeC84 said:

Got a question. Is brew needed for just building kernels? I usually use ubuntu for my builds but I would like to use osx if I could as well.

Click to expand...

Click to collapse

EverDeathly said:

this i s awesome! thanks for the guide. kinda tired of using a virtual machine to build android

Click to expand...

Click to collapse

werty100 said:

Thanks boys i am triying it on snow leopard with omnirom

Click to expand...

Click to collapse

fzr-r4 said:

sigh . . . Paranoid Android 4 completes a build for me on Mavericks, but root and wi-fi are broken. Terminal and Solid Explorer also don't work. :crying:

just putting this out there as a data point in case others try building PA on OS X.

EDIT:

i noticed that Symlink lines such as:

Symlink: /volumes/teamusb/output/android/target/product/hammerhead/system/xbin/rdev -> busybox

or

Symlink: /volumes/teamusb/output/android/target/product/hammerhead/system/bin/du -> toolbox

are resulting in those files (/system/xbin/rdev or /system/bin/du) being created in my .zip file, whereas a successful build from another user does not have those files.

this seems to be part of my problem--anyone have any guidance or similar issues?

Click to expand...

Click to collapse

joneidy said:

Now I`m getting the following error, does anyone knows if I can just manually create the missing directory to skip the error?
Thanks in advance.

Code:

host C: libbz <= external/bzip2/bzlib.c
Import includes file: out/host/darwin-x86/obj/EXECUTABLES/bsdiff_intermediates/import_includes
host C++: validatekeymaps <= frameworks/base/tools/validatekeymaps/Main.cpp
host StaticLib: libinput (out/host/darwin-x86/obj/STATIC_LIBRARIES/libinput_intermediates/libinput.a)
host StaticLib: libutils (out/host/darwin-x86/obj/STATIC_LIBRARIES/libutils_intermediates/libutils.a)
host StaticLib: libcutils (out/host/darwin-x86/obj/STATIC_LIBRARIES/libcutils_intermediates/libcutils.a)
host C: acp <= build/tools/acp/acp.c
host StaticLib: liblog (out/host/darwin-x86/obj/STATIC_LIBRARIES/liblog_intermediates/liblog.a)
host Executable: aidl (out/host/darwin-x86/obj/EXECUTABLES/aidl_intermediates/aidl)
host StaticLib: libhost (out/host/darwin-x86/obj/STATIC_LIBRARIES/libhost_intermediates/libhost.a)
host C++: aapt <= frameworks/base/tools/aapt/AaptAssets.cpp
host C++: aapt <= frameworks/base/tools/aapt/Command.cpp
host C++: aapt <= frameworks/base/tools/aapt/CrunchCache.cpp
host C++: aapt <= frameworks/base/tools/aapt/FileFinder.cpp
host C++: aapt <= frameworks/base/tools/aapt/Main.cpp
host C++: aapt <= frameworks/base/tools/aapt/Package.cpp
host C++: aapt <= frameworks/base/tools/aapt/StringPool.cpp
ld: warning: directory not found for option '-Lout/host/darwin-x86/obj/lib'
ld: warning: option -s is obsolete and being ignored
ld: unknown option: -O2
collect2: ld returned 1 exit status
make: *** [out/host/darwin-x86/obj/EXECUTABLES/aidl_intermediates/aidl] Error 1
make: *** Waiting for unfinished jobs....

Hello everyone, I`m getting the following error when trying to build Kitkat. If any help is given it will be greatly appreciated.

Code:

ldldld:::   warning:warning warning: directory:directory   notdirectory  notfoundnot   foundforfound   foroptionfor   'option-option Lout '/'-host-LoutLout///darwinhost-host/x86/darwin/darwin--objx86x86///libobjobj/'/lib
lib'ld'
:
ld ld:warning::   warningwarning:option:   -options option-  is-s  sobsoleteis   obsoleteandis   andbeing obsoletebeing   ignoredandignored
 
ldbeingld:  :ignoredunknown 
 unknownoptionld :option :-:  O2-unknown
O2 
option: -O2
collect2: ld returned 1 exit status
collect2: ld returned 1 exit status
collect2: ld returned 1 exit status
make: *** [out/host/darwin-x86/obj/EXECUTABLES/validatekeymaps_intermediates/validatekeymaps] Error 1
make: *** Waiting for unfinished jobs....
make: *** [out/host/darwin-x86/obj/EXECUTABLES/acp_intermediates/acp] Error 1
make: *** [out/host/darwin-x86/obj/EXECUTABLES/aidl_intermediates/aidl] Error 1

Click to expand...

Click to collapse

MikeC84 said:

Thanks. After running brew doctor I am not getting "ready to brew"

Code:

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
    /usr/local/lib/libosxfuse_i32.2.dylib
    /usr/local/lib/libosxfuse_i64.2.dylib

Warning: Unbrewed .la files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .la files:
    /usr/local/lib/libosxfuse_i32.la
    /usr/local/lib/libosxfuse_i64.la

Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
    /usr/local/lib/pkgconfig/osxfuse.pc

Click to expand...

Click to collapse