Package request: Android Open Source Project #21222
Labels
9.needs: package (new)
This needs a new package to be added
Comments
|
No, this is about the build environment for Android itself, rather than
Android -apps- :)
…On Sun, 18 Dec 2016, 12:43 Maarten Hoogendoorn, ***@***.***> wrote:
See
http://sandervanderburg.blogspot.nl/2012/11/building-android-applications-with-nix.html
and
http://sandervanderburg.blogspot.nl/2014/02/reproducing-android-app-deployments-or.html
Does that answer your question?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21222 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB2crCNRb2RGLuR7tpC3an5TYSSubWVfks5rJJ3cgaJpZM4LPvT_>
.
|
|
Sounds to me like a usecase for #21243 |
|
@spacekitteh ah, I misread! Apologies. In that case 👍. I'd like to build a custom build for my Samsung tablet as well ;) |
|
FWIW, I suceeded building Android on NixOS using an FHS environment: Patching all the Android source to get rid of FHS assumptions is a gargantuan and hopeless task IMHO. |
|
Hmm, are you sure that one works? It can't find ncurses, it seems. Edit: Ahh, it wants ncurses 5. Now it can't find libtinfo... ncurses should create a symlink for libtinfo. Submitted in #21350. |
|
So this is what I currently have: { pkgs ? import <nixpkgs> {} }:
let
jdk = pkgs.jdk8;
current-repo = "nougat-mr1-release";
fhs = pkgs.buildFHSUserEnv {
name = "android-env";
targetPkgs = pkgs: with pkgs;
[ git
gitRepo
gnupg1compat
python2
curl
procps
openssl
gnumake
nettools
rsync
androidenv.buildTools
androidenv.platformTools
ccache
ncurses5
jdk
schedtool
utillinux
m4
gperf
perl
libxml2
zip
unzip
bison
flex
lzop
bc
which
gcc
];
multiPkgs = pkgs: with pkgs;
[ zlib
];
extraOutputsToInstall = [ "dev" ];
runScript = "bash";
profile = ''
export USE_CCACHE=1
export ANDROID_JAVA_HOME=${jdk.home}
export LANG=C
unset _JAVA_OPTIONS
export BUILD_NUMBER=$(date --utc +%Y.%m.%d.%H.%M.%S)
export DISPLAY_BUILD_NUMBER=true
export USER=copperhead-os-build
source build/envsetup.sh
'';
};
in pkgs.stdenv.mkDerivation {
name = "android-env-shell";
nativeBuildInputs = [fhs];
shellHook = ''
cd ${current-repo}
chrt -b -p 0 $$
exec android-env
'';
}(note: requires #21368) This gets me part of the way there. I run grsecurity, however, so I have to invoke it with sudo; this results in contamination of my /root folder by So, I think the next step from here is to containerise it, because AOSP is garbage and I don't want it touching anything on my system. |
|
@abbradar did you ever run into a problem with getting "Unknown cipher suite supported by native code" errors when signing APKs during building? |
|
@spacekitteh Sadly no. FWIW I built CyanogenMod, not vanilla AOSP -- maybe some differences are in play. Anyway, do you think we can close this now? I'm not sure Android can/needs to be packaged any further than a chroot environment. |
|
Yeah, I guess. |
|
This needs to be reopened, actually. There are other issues getting it compiling on NixOS, and they probably should be figured out. The current stumbling block is what appears to be an error with OpenSSL(and LibreSSL, but I'll just say OpenSSL for short) behaving differently on NixOS compared to Debian/Arch/Ubuntu. Specifically, the conscrypt Java Crypto Provider doesn't seem to be able to work properly with OpenSSL as nixpkgs provides. It gives the following error: At first I thought it was a bug in the way OpenSSL filters worked which NixOS exposes (see #21408) but apparently not. Issue upstream in conscrypt is here: google/conscrypt#20 |
|
ping @spacekitteh @abbradar { pkgs ? import {} }:
let
jdk = pkgs.callPackage <nixpkgs/pkgs/development/compilers/openjdk/8.nix> {
bootjdk = pkgs.callPackage <nixpkgs/pkgs/development/compilers/openjdk/bootstrap.nix> { version = "8"; };
inherit (pkgs.gnome2) GConf gnome_vfs;
minimal = true;
};
fhs = pkgs.buildFHSUserEnv {
name = "android-env";
targetPkgs = pkgs: with pkgs;
[ git
gitRepo
gnupg1compat
python2
curl
procps
openssl
gnumake
nettools
rsync
androidenv.buildTools
androidenv.platformTools
ccache
ncurses5
jdk
schedtool
utillinux
m4
gperf
perl
libxml2
zip
unzip
bison
flex
lzop
bc
which
gcc
binutils
coreutils
gdb
];
multiPkgs = pkgs: with pkgs;
[ zlib
];
extraOutputsToInstall = [ "dev" ];
runScript = "bash";
profile = ''
export USE_CCACHE=1
export ANDROID_JAVA_HOME=${jdk.home}
export LANG=C
unset _JAVA_OPTIONS
export BUILD_NUMBER=$(date --utc +%Y.%m.%d.%H.%M.%S)
export DISPLAY_BUILD_NUMBER=true
'';
};
in fhs.env
bash-4.4$ ldd $(which java) linux-vdso.so.1 (0x000075585ff92000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x000075585fb53000) libz.so.1 => /usr/lib/libz.so.1 (0x000075585f93c000) libjli.so => /nix/store/xbr1i9c1gmz4if9l8g75pw6xzj7s1d9n-openjdk-8u141b15-jre/lib/openjdk/jre/lib/amd64/jli/libjli.so (0x000075585f72c000) libdl.so.2 => /usr/lib/libdl.so.2 (0x000075585f528000) libc.so.6 => /usr/lib/libc.so.6 (0x000075585f189000) /nix/store/l48biijfr1j6d5kdg911051x2phfjrz7-glibc-2.25/lib/ld-linux-x86-64.so.2 (0x000075585fd71000) |
[aosp/out/repo/host/linux-x86/bin]# paxctl -vQ ./dex2oatd PaX control v0.9 Copyright 2004,2005,2006,2007,2009,2010,2011,2012,2014 PaX Team - PaX flags: -p-s-m-x-e-r [./dex2oatd] |
|
For 6.0.x { pkgs ? import {} }:
let
jdk = pkgs.callPackage {
bootjdk = pkgs.callPackage { version = "7"; };
minimal = true;
};
fhs = pkgs.buildFHSUserEnv {
name = "android-env";
targetPkgs = pkgs: with pkgs;
[ git gitRepo gnupg1compat python2 curl procps openssl gnumake nettools
rsync androidenv.buildTools androidenv.platformTools ccache ncurses5 jdk schedtool utillinux
m4 gperf perl libxml2 zip unzip bison flex lzop bc which gcc binutils coreutils gdb python
emacs vim
];
multiPkgs = pkgs: with pkgs;
[ zlib
];
extraOutputsToInstall = [ "dev" ];
runScript = "bash";
profile = ''
export USE_CCACHE=1
export ANDROID_JAVA_HOME=${jdk.home}
export LANG=C
unset _JAVA_OPTIONS
export BUILD_NUMBER=$(date --utc +%Y.%m.%d.%H.%M.%S)
export DISPLAY_BUILD_NUMBER=true
'';
};
in fhs.env
|
|
(triage) Is this still a problem? I know someone who recently built an Android OS using the instructions at https://nixos.wiki/wiki/Android. |
|
This is definitely not a problem anymore. I have successfully built LineageOS 15.1 and 16.0, so Android 8.1 and 9.0 on NixOS. |
|
Closing for now, then. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Complete overview/guide for downloading AOSP source (including a custom kernel), building and running a QEMU image: https://www.collabora.com/news-and-blog/blog/2016/09/02/building-android-for-qemu-a-step-by-step-guide/
Build environment requirements: https://source.android.com/source/initializing.html
Source downloading: https://source.android.com/source/downloading.html
Building: https://source.android.com/source/building.html
(Included) compiler toolchain: https://source.android.com/source/jack.html
Selecting build device targets: https://source.android.com/source/devices.html
Kernel-only building: https://source.android.com/source/building-kernels.html
Running builds: https://source.android.com/source/running.html
Relevant for nixos (containers/nixops images):
QEMU kernel build script: https://android.googlesource.com/platform/prebuilts/qemu-kernel/+/master/build-kernel.sh
The text was updated successfully, but these errors were encountered: