so i want to start developing on android rom projects and i read this :
A 64-bit environment is required for Gingerbread (2.3.x) and newer versions, including the master branch. You can compile older versions on 32-bit systems.
so i want to work on 4.2.2 & i have 32bit computer it isn't possible?
Related
Currently, I think that 10.04 lucid is the "official" build platform for Android. Does anyone have any insight on if/when 12.04 will become the build platform? It seems a likely candidate because of the extra long 5 year support for both desktop and server.
The Android build is routinely tested in house on recent versions of Ubuntu LTS (10.04), but most distributions should have the required build tools available. Reports of successes or failures on other distributions are welcome.
Click to expand...
Click to collapse
http://source.android.com/source/initializing.html
Well it should work fine, I assume Google will update there Ubuntu now 12.04 is stable and LTS
Sent from my ice cream powered Nexus S
12.04 can be easiely used to build Android without any problems, I was using it already.
You can downgrade gcc and g++ to 4.4 and everything works like on 10.04, so no problems in latest version .
It's not really a question about compiling the code, but more about testing. Do you think that google will start testing the code against 12.04 with gcc 4.7 (or whatever is current) or just keep downgrading?
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Click to expand...
Click to collapse
Also from source.android.com
I thought I read something from JQB about moving to 12.04, but I don't know if this is a trivial issue or if there are major roadblocks, like java, etc. I think that 10.04 is supported until 2013 desktop/2015 server, so it might not even be this summer.
Well, I can build Android (CM9) very well with a recent Debian system.
I think what it basically comes down to is the toolchain you use (i.e. the right version of gcc, g++, etc). If your distribution doesn't have packages for the versions you need, you can always build your own ;-)
Maybe I should ask "when will JBQ upgrade his desktop machine to 12.04?"
gee one said:
It's not really a question about compiling the code, but more about testing. Do you think that google will start testing the code against 12.04 with gcc 4.7 (or whatever is current) or just keep downgrading?
Click to expand...
Click to collapse
You do know that the x86/x64 toolchain in your system is not used by the android build system ? You can't use output of that on any of the currently supported android phones. check the /prebuilt directory for the cross compile toolchains used by android which should work fine on any linux system.
I used @viulian's port of PHP 5.3.8 and 5.4.2 of PHP and lighttpd on my Galaxy S2. It ran like a charm on Android 2.3.3.
But since I upgraded to ICS 4.0.3 the PHP didn't run anymore and reported it to @viulian. He discovered he used the wrong compiler switches and recompiled it and it ran again but some functions regarding directories (dir(), scandir() ) don't run properly due to a 64 bits filename problem. This is also described in https://bugs.php.net/bug.php?id=27792 . Thanks, @viulian for your effort ! He could not test it as he has no ICS test development yet.
Now I decided to compile PHP myself. I have downloaded the sources from php.net and installed the Android dev kit with cross compilers and installed the ARM cross compiler on Macports as well (I use a Mac running Lion 10.7, but I have Ubuntu 12.04 in a VMware session if that suits better) .
Can somebody tell me what to do to properly compile PHP myself to make a single PHP binary ?
I cannot find proper answers by googling around.
Hi there!
I would like to compile android apps and ROMs on my nexus 9, but to do so I would need to emulate a 64 bit system like amd64: I know I can use AIDE to create apps but I prefer using Android studio and I would also like to compile multirom for another device, and as far as I know there is no way to run an android build environment natively in android, so I was thinking of emulating an amd64 in my kali nethunter chroot using qemu. I installed qemu-user-static and executed the qemu-debootstrap command to create a basic ubuntu amd64 rootfs, but then the second stage gave me an error that basically meant that qemu couldn't emulate amd64.
Now my question is: does anybody know where can I find the qemu-system-amd64 binary for aarch64 (or how can I build it)?
Thanks in advance,
Daniil Gentili
The nexus 9 can't emulate AMD64
Well as far as I know
I believe there aren't any prebuilt binaries. AArch64 is relatively new in the Linux world.
It's possible, but will be really slow (I don't own a Nexus 9, using common sense and knowledge here)
Doing it won't be easy. You have two options:
- create a proper Linux chroot on your device, then install qemu in it
Previously I created a Gentoo armv7 chroot on a Tegra 3 device. It worked surprisingly well. Things compile, albeit very slowly.
- Compile QEMU directly on Android, however Android uses bionic libc, not glibc. You may need to port it yourself, AFAIK no one's done that.
Sent from my LG-H812 using Tapatalk
Hello!
I've compiled various ROMs from source without issue (well many issues and a lot of reading on this forum to troubleshoot). I am running Ubuntu 16.04.2 LTS and have always followed Android's Guide for installing the required build packages. The guide specifies running Ubuntu 14.04. I read on another website specifically for 16.04, and the recommended build packaged are different. Lastly, when reviewing LineageOS wiki for build packages, they have an even different list. The LineageOS guide did not actually work when I tried to install the build packages they listed.
Can anyone help clarify this? Is there a single source of truth for knowing which build packages are required for the version of Linux?
EDIT: So I somewhat answered my own question by looking into each package that was different from Android's Development webpage. But I still do not know how one would know which packages you'd need when working with various ROMs.
I do realize that Virtualbox has Android x86 VM compatibility.
What do experts and intermediates use to learn and test andorid custom roms & features?
I mean for a beginner, making mistakes on their regular device could lead to fatal consequences, constant reflashing and being unable to use stock rom for general purposes.
Should a novice aiming to learn how to create custom roms and features use their own device, despite the consequences or is there a better approach to this?
Additionally, in case virtualization is recommended, what software should be used to resemble a real device as much as possible (especially firm specific phones like Oneplus)
VirtualBox - and all emulators based on it, yes almost all wellknown emulators are based on it - is x86 / x86_64 specific, the Android images run on it have to be compiled as x86 / x86_64 ports. Emulators designed to be run on x86 / x86_64 computers aren't meant to be used as a tool for creating / testing an Android ROM, IMHO.
Virtualization ( read: Hardware Assisted Virtualization - HAV ) is a x86 / x86_64 CPU specific feature ( what you enable / disable in computer's BIOS ) - it simply allows different OS to be run simultaneously on computer: No real ARM-CPU based Android device has this feature. That's why you don't have to worry about it when developing an Android ROM.
jwoegerbauer said:
VirtualBox - and all emulators based on it, yes almost all wellknown emulators are based on it - is x86 / x86_64 specific, the Android images run on it have to be compiled as x86 / x86_64 ports. Emulators designed to be run on x86 / x86_64 computers aren't meant to be used as a tool for creating / testing an Android ROM, IMHO.
Virtualization ( read: Hardware Assisted Virtualization - HAV ) is a x86 / x86_64 CPU specific feature ( what you enable / disable in computer's BIOS ) - it simply allows different OS to be run simultaneously on computer: No real ARM-CPU based Android device has this feature. That's why you don't have to worry about it when developing an Android ROM.
Click to expand...
Click to collapse
You're right, ARM is the right cpu arch.
I dont understand your last sentences, Why does HAV matter in terms of developing android ARM roms?
Also if I am developing for arm(v8) devices, yet virtualize x86_64 on my pc to test my first custom rom, how does that port well? It shouldnt work right?
Now it is up to me who does not understand what role HAV should play in the development of a custom ROM for Android. It's an x86 / x86_64 emulator which makes use of this feature, if ever.
Look inside here to get an idea what HAV is, how it works.