Topic

docker

A collection of 4 issues

mosh/Android build VM

To Download the VM image: docker pull ddrown/mosh-build To build mosh binaries: OUTPUTDIR=~/target mkdir $OUTPUTDIR docker run -v $OUTPUTDIR:/target ddrown/mosh-build This will create 6 binaries in $OUTPUTDIR/bin: mosh-client.arm.nopie, mosh-client.arm.pie, mosh-client.x86.nopie, mosh-client.x86.pie, mosh-client.mips.nopie, and mosh-client.mips.

Busybox/Android build VM

I took the Android Cross Compile VM [https://blog.dan.drown.org/android-cross-compile-environment/] and created a docker VM image for just building busybox. To Download the VM image: docker pull ddrown/busybox-build To build busybox binaries: OUTPUTDIR=~/target mkdir $OUTPUTDIR docker run -v $OUTPUTDIR:/target ddrown/busybox-build This will create

Updated busybox builds

I rebuilt busybox and upgraded to 1.22.1. The new Android L developer preview requires binaries built with PIE [http://en.wikipedia.org/wiki/Position-independent_code]. Android 4.1 is the oldest version that works with PIE binaries. This means two builds per CPU architecture are needed. Android 4.

Android Cross Compile environment

I took my Android ports build environment and turned it into a docker image. To download it (should be around 2.3GB), install docker on Linux and then run: # docker pull ddrown/android-cross-compile Pulling repository ddrown/android-cross-compile c9c1ce340d35: Download complete 511136ea3c5a: Download complete 34e94e67e63a: Download complete 0c752394b855: Download complete dea657cfb317: