I now this thread is a bit old, but there may be some people able to solve my problem here..
Originally Posted by unrandomsam
. build/env_setup.sh (Make sure your SHELL is bash(Or at least not zsh)
make mkbootimg mkbootfs fastboot adb
(If you have to do a full build you can but for few tools might as well not).
That works indeed! And I am on OS X with MacPorts. Thanks guys!
Now… I needed to compile a different mkbootimg, the one that makes use of md5, for the bcm21553 CPU family. I had the full directory with the Android.mk and the .c file. I solved removing the mkbooting directory from the AOSP and putting this new one instead.
Isn't there any other way? I hoped it was just a matter of writing make in the new module/tool directory after setting the environment but such isn't the case.
And another thing: what the heck are the .mk files?? Are they specific to the Android SDK? I can't find anything in Internet.