Related
After googling this topic and finding nothing, I figured XDA was the place to go. I am looking for a way to get a C++ compiler working on my phone (mytouch slide) or android in general.
Thanks in advance
Que? Like a C++ compiler to compile for android? Why would u want this C++ don't run native on Android it must be called from java so it would be pointless.
There is an sdl port around that required zero knowledge of.java but I believe it still has to compile the java each time. If not it could be possible...
Sent from my Nexus One
I don't want to run the programs on my phone, just compile
Compile for what?
What is the Android NDK?
The Android NDK is a toolset that lets you embed components that make use of native code in your Android applications.
Android applications run in the Dalvik virtual machine. The NDK allows you to implement parts of your applications using native-code languages such as C and C++. This can provide benefits to certain classes of applications, in the form of reuse of existing code and in some cases increased speed.
The NDK provides:
* A set of tools and build files used to generate native code libraries from C and C++ sources
* A way to embed the corresponding native libraries into an application package file (.apk) that can be deployed on Android devices
* A set of native system headers and libraries that will be supported in all future versions of the Android platform, starting from Android 1.5
* Documentation, samples, and tutorials
The latest release of the NDK supports these ARM instruction sets:
* ARMv5TE (including Thumb-1 instructions)
* ARMv7-A (including Thumb-2 and VFPv3-D16 instructions, with optional support for NEON/VFPv3-D32 instructions)
Future releases of the NDK will also support:
* x86 instructions (see CPU-ARCH-ABIS.TXT for more information)
ARMv5TE machine code will run on all ARM-based Android devices. ARMv7-A will run only on devices such as the Verizon Droid or Google Nexus One that have a compatible CPU. The main difference between the two instruction sets is that ARMv7-A supports hardware FPU, Thumb-2, and NEON instructions. You can target either or both of the instruction sets — ARMv5TE is the default, but switching to ARMv7-A is as easy as adding a single line to the application's Application.mk file, without needing to change anything else in the file. You can also build for both architectures at the same time and have everything stored in the final .apk. For complete information is provided in the CPU-ARCH-ABIS.TXT in the NDK package.
The NDK provides stable headers for libc (the C library), libm (the Math library), OpenGL ES (3D graphics library), the JNI interface, and other libraries, as listed in the section below.
The NDK will not benefit most applications. As a developer, you will need to balance its benefits against its drawbacks; notably, using native code does not result in an automatic performance increase, but does always increase application complexity. Typical good candidates for the NDK are self-contained, CPU-intensive operations that don't allocate much memory, such as signal processing, physics simulation, and so on. Simply re-coding a method to run in C usually does not result in a large performance increase. The NDK can, however, can be an effective way to reuse a large corpus of existing C/C++ code.
Please note that the NDK does not enable you to develop native-only applications. Android's primary runtime remains the Dalvik virtual machine.
The ndk allows u to use c++ c/c++ code in Android. That code must be called from java tho.
Sent from my Nexus One
I don't think you guys are understanding his question... He's not looking to write apps for Android... he's writing stuff in C++ (presumably for desktop or maybe other embedded applications, I dunno) and just wants to be able to compile that code on his Android device...
Now as far as an answer to that question, they did kinda cover it... Since pretty much everything in Android runs in Java, I believe it would be pretty difficult to write a C++ compiler that could run on Android.
To install an compiler in your Android device, google around for how to install Debian in it. Don't be afraid, you install it in parallel of Android, you will need a command or terminal window as well (available in the marketplace).
Debian comes with everything you need to compile in your device.
I hope I was useful.
Cheers
Thank you abrigham for clearing that up for me. You are exactly correct.
Ernestus, that seems like it would cause more problems then it would be worth
hmm.. i was googling for this as well.. thought it'll be useful to have this around.
JDV28 said:
Thank you abrigham for clearing that up for me. You are exactly correct.
Ernestus, that seems like it would cause more problems then it would be worth
Click to expand...
Click to collapse
Next best option then is to cross-compile to Android/ARM from another platform. The arm-eabi toolchain provided by Google's NDK is one option as others have already mentioned.
Codesourcery ARM toolchain is another, for Linux i686 theres link to the downloadable archive see this post (search for 'wget THISLINK' text on that page).
- jc
If your looking to corss compile for android, check this link out.
http://teslacoilsw.com/dropbear
Installing debian isn't too bad, and would give you the most flexibility for compiling on the phone.
You could also ssh into another computer using connectbot or some other terminal and code/compile remotely.
Another way to do remote compiles is continuous integration. Edit/upload the file to your repository, and using a server such as Jenkins, run the compile and view the results through the browser or an app such as Hudson2Go. Jenkins will also auto-compile on edits and can send you a text if the build fails. Jenkins is very easy to setup.
Try finding an online c++ compiler or you could connect to a windows or linux machine/server to upload andcompile your c++ files.
JDV28 said:
After googling this topic and finding nothing, I figured XDA was the place to go. I am looking for a way to get a C++ compiler working on my phone (mytouch slide) or android in general.
Thanks in advance
Click to expand...
Click to collapse
Use "c4droid" this is a paid app.. anywy if you like search on the market.
Another alternitiv is out there now. Not sure how good it works.
C / C++ Compiler
im looking for compiler too i found i market a4droid compiler but it costs... and i couldnt find enywhere free apk
Easiest thing to do would be a chroot Linux environment from an existing distribution, like Ubuntu. Then compilers for nearly any language you can think of are an "apt-get install" away.
If you're running CyanogenMod 7, you have a large SD card, and you don't mind repartitioning the SD card and shaving off 2 GB or 4 GB for Linux, then I'll be posting a howto in the next day or two. I have Ubuntu 11.10 Oneiric Ocelot running out of /sd-ext cleanly, using only files from official sources (<32 MB file from cdimage.ubuntu.com and everything else via apt/dpkg with signature verification) rather than from rapidshare-like sites.
Or about a year ago there were instructions posted for unzipping a ~2 GB image containing an older version of Ubuntu downloaded from a filesharing site. You could do that if you have an immediate need.
you can download from my blog
http://dateno1.egloos.com/855501
it from https://market.android.com/details?id=com.n0n3m4.gcc4droid&feature=more_from_developer
it has some library problem but work well (i already compile few binary for my phone )
I think c4droid maches perfectly what you were looking for. I'm using it to work on my projects "on the road" and so far it works pretty well.
A little tricky to set up, since you need "gcc plugin for c4droid" but to choose g++ compiler, and builds are saved at "data/data/com.n0n2m3.c4droid/files/temp" or something like that...
There's another option, but you still have to pay: DroidEdit Pro. Perhaps better editor (didn't test it though) but without it's own compiler, you have to set up an external compiler from sftp server.
Is there any way to compile java applications in android?
i wanna write simple java applications like i do in ms-dos
"javac file.java, java file".
could somebody tell me if i can do it?
Meraklis56 said:
Is there any way to compile java applications in android?
i wanna write simple java applications like i do in ms-dos
"javac file.java, java file".
could somebody tell me if i can do it?
Click to expand...
Click to collapse
if you want to build an app of course you can but i don`t know if that`s so simple. depends on knowledge
but you can start here:
1. http://developer.android.com/sdk/index.html
2. http://www.eclipse.org/downloads/
3. you will need java too
are you sure i do this on my mobile?
if i got it,right this is how i make application in my pc,not in my xperia!
i want that, in my android
Meraklis56 said:
are you sure i do this on my mobile?
if i got it,right this is how i make application in my pc,not in my xperia!
i want that, in my android
Click to expand...
Click to collapse
ohhh you won`t specify
download terminal emulator from market and you will have access to shell through phone
well u cant , cause Android doesnt have a JVM , it has a Dalvik Virtual Machine, and its optmized for mobile aplications and for the hw of the device, but u can emulate some plataform, but if u want to compile just some java code, there some solutions in the forum like install ubuntu and compile there, but an aplications native for android is a lil' hard
edit---
you can read this, is very helpfull...
http://en.wikipedia.org/wiki/Dalvik_(software) Dalvik VM
http://developer.android.com/reference/java/lang/Compiler.html Compiler API ANDROID (u can use it =) in ur aplication)
installing/emulating ubuntu just for compiling java is a bit out of my limits!
i dont want to compile any crazy program, just some easy programs.
there is not other solution, than this?
java compilation on android device
I'm looking to do likewise for various reasons.
One is I live in a tent and the droid device consumes less power than my laptop.
Two is that I'm developing a platform that moves some 'programmer space' activities to user space. Though with java the later can normally be accomplished wo authoring any source or compiling by using introspection and object serialisation (granted an android based dx is needed here) there are use levels of the platform that afford source authoring and compilation.
Having said that as far as I can tell a javac for android is in order.
Thus: openjdk.java.net/groups/compiler/README.html
One needs to verify the source's class dependencies and see if the android vm (the dalvik vm really) implements those classes. If and where not either the compiler code needs to be modified to use dalvik implemented java classes or the dalvik vm extended to accommodate the additional classes, again if any, that the javac source uses.
The determination as to which direction to take need consider the effort involved
either way and the legalities of either way while noting that the dalvik vm is allready the subject of a lawsuit (see Controversy at en.m.wikipedia.org/wiki/Dalvik_(software) ).
Personnaly I'm leaning to modify the javac source if necessary as this
openjdk.java.net/legal/
doesn't look prohibitive in so long, I think, as the language specs are met or more simply.in so long as the modified to run on android javac produces the same results as the original.
If you're ready to get yor hands dirty (not all coding is drag and drop) here ya go
download.java.net/openjdk/jdk6/
Maybe we'll meet somewhere along the way.
Sp
I got ClassCycle and ran it on the classes that resulted from me compiling the javac sources
in the openjdk's langtools directory . These sources are a programatic interface to javac and
are said to be used at one's own risk.I had trouble compiling the 'actual' sources
but will try again.
Once I can make heads or tails of the ClassCycle report I can provide a list
of javac's class deps.
Why one might ask would is any of this class deps stuff needed?
Dx the Java bytecod+e and run it. Droid has a vm, should be ok.
The problem is that Dalvik, at least does not implment awt and swing. What this means is that there is no native implementation for those classes' bytecode to be runtime instantiated towards.
Likewise if there are javac class deps that the dalvik vm does not implement there will be no native implementation in those areas and the bytecode won't run.
Till I get the list,
Steve
Script Layer for Android
Meraklis56 said:
Is there any way to compile java applications in android?
i wanna write simple java applications like i do in ms-dos
"javac file.java, java file".
could somebody tell me if i can do it?
Click to expand...
Click to collapse
For rooted systems there is a way to run Ubuntu in the phone/tablet. I don't remember the details, just google for it. I only remember that you should use a VNC viewer to connect to the xserver running in your own system.
I don't know if you can access from that Ubuntu to the resources of your Android (sensors, GPS, camera, and so on).
If you want to be able to create small programs in an easy way for your Android and being able to access all sensors and peripherals of your phone you should consider using SL4A (Script Layer for Android).
It's a base scripting system. On top of it you can install Python, PHP, Bash. So you can write your own scripts using any text editor in the phone, and run it without using any computer in the process
java compilation on android device
A year later and:
JavaIDEDroid: http://code.google.com/p/java-ide-droid
AIDE: https://play.google.com/store/apps/details?id=com.aide.ui&hl=en
and probably others as well.
Hi guys, I would like to ask you what IDE's and other software I need to make and modify android roms. I am particularly looking at helping with ICS production. I know java and some C++ if this helps, I am unsure of what to use whether that be eclipse or some other IDE/SDk. Also there are a few file types I am unfamiliar with and want to know how to edit those such as .so's and other files. Thanks P500 community you guys are awesome D
If you haven't already, I'd highly reccomend setting up a build environment and trying to sync the cm repos. Once you have the code, you can play around and see what you need from there, in terms of an IDE.
Sent from my LG-P500 using XDA
Fantastic, I shall get onto that right away.
May the force be with you, bro!
Sent from my LG-P500 using Tapatalk 2
gymfreak7855 said:
Hi guys, I would like to ask you what IDE's and other software I need to make and modify android roms. I am particularly looking at helping with ICS production. I know java and some C++ if this helps, I am unsure of what to use whether that be eclipse or some other IDE/SDk. Also there are a few file types I am unfamiliar with and want to know how to edit those such as .so's and other files. Thanks P500 community you guys are awesome D
Click to expand...
Click to collapse
gymfreak7855 said:
Hi guys, I would like to ask you what IDE's and other software I need to make and modify android roms. I am particularly looking at helping with ICS production. I know java and some C++ if this helps, I am unsure of what to use whether that be eclipse or some other IDE/SDk. Also there are a few file types I am unfamiliar with and want to know how to edit those such as .so's and other files. Thanks P500 community you guys are awesome D
Click to expand...
Click to collapse
Read some android books.you already know c++ and Java so you will become good dev.
For playing with code you need.
Ubuntu.
Notepad.
sdk & adb.
And this "good luck!"
Yeah! Actually even i am interested in learning.
I know c/c++. No java yet
I'll be finishing my exams on the 3rd of may and would have around 2 months of vacations to learn
So guidance would really be appreciated. Do we need a separate sdk for linux based os? I have sdk on windows, isnt that enough?
What is the advantage of using linux for android development? I have backtrack(ubuntu based) on vmware. Will it do?
Essential Software:
Ubuntu 11.10 (dual boot not virtual machine, it's too slow)
Eclipse IDE with the Android plugins
Meld (for easy directory compares)
Mastery of the terminal especially git / repo commands
Github account
CyanogenMod gerrit account
Google Plus account
I'm assuming you're coming from Windows since you don't know what a .so file is (like I did when starting). .so files are android's versions of .dll files. 'executables' don't have a file extension. Kernel modules use the .ko extension.
(I think .so means shared object, .ko means kernel object. Makes sense to me anyway )
The worst thing about starting is simply the sheer size of the project, it is a whole operating system we are dealing with here!
Start simple and easy, follow the instructions on how to make your own build and flash it. (and feel proud you have your own build string in about phone!) Then do it again without the instructions. (harder than it sounds )
The programming side may not be such a problem for you if you already know it. I didn't know anything. reading library files written in c++ ain't so bad, but getting used to how an android app is written in java was a huge mindf**k for me at first.It still is actually
I'm really just your average code hacker, I just hack based on educated guesses but I have taken copious notes on what I do and how things work. Seriously, I have two A5 notebooks full of lists, commands, file locations, diagrams and other tips I've found over the past 6 months.
Prepare to read a lot, be confused a lot, say WTF?!?!?! a lot, delighted when you make your first changes and they work, a ton of waiting for builds to finish and perhaps a bit nervous when you are ready to submit your first commit to CyanogenMod...
Can't we practice on something less taxing than the the whole cyanogenmod, like maybe some prebuilt system apps?
I have allocated 2.9gb of ram and enough cpu to my vm for it to run smoothly so speed isn't really an issue here
Will backtrack do or would ubuntu be better(backtrack is a network security related os based on ubuntu only)
And how important is java. I have two months of almost pure vacations(just have to make a project) so time wont be much of an issue and i'll anyway be doing java in a year or two at college so starting now wont be any harm.
BTW just curious why is g+ account an essentiality here?
Edit
Oh and yeah ill be switching from win to linux and that IS going to be a pretty big problem :/
I don't even properly know what a kernel is and what it does.
Edit2
Iv added you to my circles adfad please add me.
These guides could help!
http://forum.xda-developers.com/showthread.php?t=1272270
http://forum.xda-developers.com/showthread.php?t=667298
I'm starting learning too. I already know the android framework and java.
I have some problems when I try to compile for a device.
Code:
[email protected]:~/WORKING_DIRECTORY$ source build/envsetup.sh
including device/moto/wingray/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/toro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
It doesn't include device/cm_device_lge_p500/vendorsetup.sh (I'm using androidmeda's sources) and if I run "lunch":
Code:
[email protected]:~/WORKING_DIRECTORY$ lunch
You're building on Linux
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. full_maguro-userdebug
5. full_toro-userdebug
6. full_panda-eng
7. cm_anzu-userdebug
8. cm_captivatemtd-userdebug
9. cm_coconut-userdebug
10. cm_crespo-userdebug
11. cm_crespo4g-userdebug
12. cm_epicmtd-userdebug
13. cm_galaxysbmtd-userdebug
14. cm_galaxysmtd-userdebug
15. cm_galaxys2-userdebug
16. cm_haida-userdebug
17. cm_hallon-userdebug
18. cm_i777-userdebug
19. cm_iyokan-userdebug
20. cm_mango-userdebug
21. cm_maguro-userdebug
22. cm_p1-userdebug
23. cm_p1c-userdebug
24. cm_p3-userdebug
25. cm_p4-userdebug
26. cm_p4tmo-userdebug
27. cm_p4vzw-userdebug
28. cm_p4wifi-userdebug
29. cm_p5-userdebug
30. cm_p5wifi-userdebug
31. cm_p920-userdebug
32. cm_p970-userdebug
33. cm_p990-userdebug
34. cm_p999-userdebug
35. cm_pyramid-userdebug
36. cm_satsuma-userdebug
37. cm_shooter-userdebug
38. cm_shooteru-userdebug
39. cm_smb_a1011-userdebug
40. cm_smultron-userdebug
41. cm_tenderloin-userdebug
42. cm_tf101-userdebug
43. cm_tf201-userdebug
44. cm_toro-userdebug
45. cm_urushi-userdebug
46. cm_vibrantmtd-userdebug
47. cm_wingray-userdebug
48. cm_zeus-userdebug
Which would you like? [full-eng]
There isn't our phone.
I think it can't know I've added another device. Does anybody know how to solve this problem? I'm sure it's something pretty stupid...
P.S. I'm using Ubuntu 11.10
EDIT: Ok, I think I've done something wrong syncing androidmeda sources.
What I've done is:
Code:
[email protected]:~$ cd WORKING_DIRECTORY
[email protected]:~/WORKING_DIRECTORY$ repo init -u git://github.com/androidmeda/cm_device_lge_p500.git
repo initialized in /home/francesco/WORKING_DIRECTORY
[email protected]:~/WORKING_DIRECTORY$ repo sync
Fetching projects: 100% (248/248), done.
Syncing work tree: 100% (248/248), done.
I've done this for git://github.com/androidmeda/cm_vendor_lge_p500.git and git://github.com/androidmeda/lge-kernel-msm7x27.git too. I can't see them though.
Solved the problem. Cloned androidmeda's device folder into device/lge/p500
EDIT2: FINALLY COMPILING!
EDIT3:
Code:
make: *** Nessuna regola per generare l'obiettivo "device/lge/p500/init.p500.usb.rc
It's 'No rule to make target'. I don't know what to do, I can't even find that file, but I've got a file called init.thunderg.usb.rc
Solved renaming init.thunderg.usb.rc to init.p500.usb.rc. It's compiling now
adfad666 said:
Essential Software:
Ubuntu 11.10 (dual boot not virtual machine, it's too slow)
Eclipse IDE with the Android plugins
Meld (for easy directory compares)
Mastery of the terminal especially git / repo commands
Github account
CyanogenMod gerrit account
Google Plus account
I'm assuming you're coming from Windows since you don't know what a .so file is (like I did when starting). .so files are android's versions of .dll files. 'executables' don't have a file extension. Kernel modules use the .ko extension.
(I think .so means shared object, .ko means kernel object. Makes sense to me anyway )
The worst thing about starting is simply the sheer size of the project, it is a whole operating system we are dealing with here!
Start simple and easy, follow the instructions on how to make your own build and flash it. (and feel proud you have your own build string in about phone!) Then do it again without the instructions. (harder than it sounds )
The programming side may not be such a problem for you if you already know it. I didn't know anything. reading library files written in c++ ain't so bad, but getting used to how an android app is written in java was a huge mindf**k for me at first.It still is actually
I'm really just your average code hacker, I just hack based on educated guesses but I have taken copious notes on what I do and how things work. Seriously, I have two A5 notebooks full of lists, commands, file locations, diagrams and other tips I've found over the past 6 months.
Prepare to read a lot, be confused a lot, say WTF?!?!?! a lot, delighted when you make your first changes and they work, a ton of waiting for builds to finish and perhaps a bit nervous when you are ready to submit your first commit to CyanogenMod...
Click to expand...
Click to collapse
Thanks man Your work has really inspired me and yes haha I am moving from windows all though I have had some experience with ubuntu before. It makes sense about the extensions. Thanks for your advice Will ask questions if I need to
I'm having problems compiling using make -j4
Code:
make -C kernel/lge/p500 O=/home/francesco/WORKING_DIRECTORY/out/target/product/p500/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=/home/francesco/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- cyanogenmod_p500_defconfig
make[1]: ingresso nella directory "/home/francesco/WORKING_DIRECTORY/kernel/lge/p500"
make[1]: *** Nessuna regola per generare l'obiettivo "cyanogenmod_p500_defconfig". Arresto.
make[1]: uscita dalla directory "/home/francesco/WORKING_DIRECTORY/kernel/lge/p500"
make: *** [/home/francesco/WORKING_DIRECTORY/out/target/product/p500/obj/KERNEL_OBJ/.config] Errore 2
make: *** Attesa per i processi non terminati....
'No rule to make target "cyanogenmod_p500_defconfig". Stop'
Any idea?
When I've used make -i I haven't had this problem
EDIT: Solved moving cyanogenmod_p500_defconfig in p500 folder
Ok, I'm trying to tidy up everything a bit. I've noticed there is a new github. I've seen this:
Code:
LG P500 ICS Setup
Copy/paste it WORKING_DIR/.repo/local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/p500" name="p500/cm_device_lge_p500" remote="github" revision="master" />
<project path="vendor/lge/p500" name="p500/cm_vendor_lge_p500" remote="github" revision="master" />
<project path="kernel/lge/p500" name="p500/lge-kernel-msm7x27" remote="github" revision="android-ics-msm-2.6.35" />
</manifest>
I have no local_manifest.xml. Do I have to create it? Or do I have to add these three lines to manifest.xml (which is in .repo folder)? And do I have to add toolchain too?
Question: if installing Ubuntu with wubi on Windows XP, will it show the dual-boot screen on every boot?(or else what shortcut?)
And does it need to defragment, or is it safe just like that?
vlt96 said:
Question: if installing Ubuntu with wubi on Windows XP, will it show the dual-boot screen on every boot?(or else what shortcut?)
And does it need to defragment, or is it safe just like that?
Click to expand...
Click to collapse
No idea, never tried.
If you understand anything:
http://en.wikipedia.org/wiki/Wubi_(Ubuntu)
Why dont you use vmware instead?
Now someone help me with this:
Whenever i try to recompile the framework-res.apk(pasquale test)(even without editing) i get this error:
What can i do about it?
rishabh22 said:
No idea, never tried.
If you understand anything:
http://en.wikipedia.org/wiki/Wubi_(Ubuntu)
Why dont you use vmware instead?
Now someone help me with this:
Whenever i try to recompile the framework-res.apk(pasquale test)(even without editing) i get this error:
What can i do about it?
Click to expand...
Click to collapse
VM got me an error when installing saying it is incompatible with win xp (I could install, but didn't wanna risk, windows is harder to recover than Android)
try using virtual box.
https://www.virtualbox.org/
rishabh22 said:
try using virtual box.
https://www.virtualbox.org/
Click to expand...
Click to collapse
yea I did that... but did anyone try it on XP, it says it failed incompatibility tests or something (same error I got when trying to install windows 7 video drivers on xp) and I don't wanna risk, anyone?
I don't think it's good to install ubuntu to compile android in a virtual machine, I think the compilation would be too slow. I'm sorry I can't help you, I've installed ubuntu from a Live CD and I didn't have many problems with the installation process.
BTW, added the three lines to manifest.xml synced repo. It's compiling well using make -j4
vlt96 said:
yea I did that... but did anyone try it on XP, it says it failed incompatibility tests or something (same error I got when trying to install windows 7 video drivers on xp) and I don't wanna risk, anyone?
Click to expand...
Click to collapse
huh? both vmware and virtual box arn't compatible with xp
why the heck were u trying to install win7 video drivers on xp
And why dont you dual boot?
---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------
ZatBaloo said:
I don't think it's good to install ubuntu to compile android in a virtual machine, I think the compilation would be too slow. I'm sorry I can't help you, I've installed ubuntu from a Live CD and I didn't have many problems with the installation process.
BTW, added the three lines to manifest.xml synced repo. It's compiling well using make -j4
Click to expand...
Click to collapse
if you have enough ram and a good enough processor there shouldnt be any problem in using a virtual machine. i use backtrack with 2.9/4gb ram and am able to use both windows7 and backtrack simultaneously without any problems/lag
I have an i5 2.3-2.9GHz
Sure it depends on what you want to compile. It was just a suggestion to compile faster. You probably won't notice lag, but it will take more to compile everything.
How does the AOSP and the Android SDK relate?
If I repo the AOSP do I by default now have the SDK?
Do I have to download it separately?
Or can I/Should I compile it from the AOSP?
I ask because after following the instructions up until: source.android.com/source/building.html. I successfully compiled full-eng and ran the emulator and everything works just fine. It also seems like adb is installed which from what I understand is a part of the SDK. I can't seem to find an answer to this.
So I am going to do my best at answering my own questions and posting for the benefit of anyone else who may be confused; if any of the statements I make are wrong feel free to correct me. This is just from my experience. There seems to be little information regarding how the two relate excepting the build/core/build-system.html, and sdk/docs/howto_build_SDK.txt included with AOSP and airtower.wordpress.com/2010/07/25/building-the-android-sdk/ and of course, trial and error.
NB: jindroid.com/2009/06/08/howto-build-sdk-from-android-source-code/ points to documentation that has since moved to the above location it seems. At least it wasn't there for me as of the most recent repo sync against master.
rpowell8 said:
How does the AOSP and the Android SDK relate?
Click to expand...
Click to collapse
The android SDK is a subset of the ADT (Android Developer Toolkit). The SDK as you download it today is basically just a few binarys for getting the actual content SDK.
I think the best way to describe the SDK is that it is divided into to parts tools, and libraries. The tools are for managing the sdk (tools/android) and misc tools to build apk's, align them, emulate an api etc, and then there are the tools in platform-tools which allow you to perform operations on your device (adb fastboot etc). The "libraries" are a set of API's , system images (file for running an android virtual device (emulator)), and documentation for each release of Android. These seem to reside under platform/
You can either download the above components from the command line, or from eclipse. Eclipse is actually included in the ADT as well with the plugin for android apps preloaded. If you don't have the plugin, you can get it vie Help/Install New Software. This launches what seems to be a front end for the android SDK Manager which allows you to graphically choose which platforms you want to support and emulate.
Now, how does the SDK (the tools and libraries) relate to the AOSP as you repo init/sync from the master repository? It seems you can't build apps from the code downloaded from the AOSP git repo (I'm not sure about this but doesn't seem like it). Instead, what you do, is you use the AOSP to build the SDK (NB: when you use the SDK Manager as mentioned above, you are getting prebuild SDKs, if you want to build the SDK yourself you use the AOSP code) as described in the above mentioned howto. Once the build for the Android SDK is complete it is located in out/host/linux-x86/sdk or similar directory. You can actually point the eclipse plugin to this directory as the location for the SDK...but I recommend using the .zip file that is in that directory and putting it somewhere other than the out directory. Reason being if you decide to do a lunch full-eng after you did the lunch sdk-eng, and then proceed to make, it will force a make cleaninstall and that will basically do a rm -rf on the out directory, deleting all of your SDK and any other platforms you downloaded through the sdk manager.
After you've built the sdk, you now have the necessary tools and API's to build for the platform you repo'd. A word of warning is that it seems if you repo the master branch, it is labeled as "AOSP" for the version indicating to Eclipse that the minimum platform required is the one you just built and so if you want to run it on your device you'll need the full platform loaded onto it or it will show you are running a version earlier than AOSP (also called 'Preview'). Example, as of this writing the version of AOSP is 4.2.1 and the API level is 17 (An API level is just a set of functions/datastructures available for a particular release of Android OS, so for Level 17 it corresponds to 4.2, You can use a higher API than your target (accept in the case of AOSP Preview) and still make sure you are compatible, but you can't use a lower API and expect to have functions/datastructures that were only implemented in later versions of Android). If you have downloaded the Android SDK for API level 17 it will be 4.2, not 4.2.1. You will not be able to run your app that you built using the API level 17 "Preview" based on 4.2.1...on your 4.2 emulator (or device for that matter). You will need to use the emulator based on the AOSP Preview build.
So in short the AOSP contains the sources to build the SDK, but you can also get prebuilt SDK's if you don't want to go through and build each API level.
rpowell8 said:
If I repo the AOSP do I by default now have the SDK?
Click to expand...
Click to collapse
No, you have the components to /build/ the SDK
rpowell8 said:
Do I have to download it separately?
Click to expand...
Click to collapse
No, you can either build it from the AOSP, or you can download it separately.
rpowell8 said:
Or can I/Should I compile it from the AOSP?
Click to expand...
Click to collapse
Probably should if you're building against the latest android development, but I don't see the need if you are building apps for already released API levels.
--- copied with permission from nathanpfry.com ---
---If you would prefer a Builduntu install disc, click here to check out this post for an ISO---
BuilduntuVM is a custom branch of the Ubuntu operating system for compiling Android ROMs from source. It includes everything you need to sync with the repo of your choice (Cyanogenmod, AOSP, etc) and start building.
Features:
- Xubuntu 16.04 base
- Installed all necessary software for compiling (list available in the guide link above)
- Unnecessary programs removed (media players, games etc.)
- Geany for editing code
- Repo located in ~/bin and added to PATH
- Quick access drop-down terminal (Ctrl-F12)
All you have to do is download the source!
The only requirement is that your host machine supports a 64 bit OS. 32 bit systems will not work!
Instructions:
1. Download and install VirtualBox for your host system from here.
2. Download the latest builduntu zip archive and extract builduntu.ova to your hard drive.
3. Start VB, click File > Import Appliance. Select "Open Appliance" and choose builduntu.ova, then click Next to import the virtual machine.
4. Highlight builduntu in VirtualBox Manager and open Settings. Under "System" you will want to give it more RAM and Processor Cores. The higher these values are, the faster you will compile ROMs.
5. Start the machine, pull up a terminal and initialize a git repo. Once the source is finished downloading, you're ready to go!
Download:
Click here for mirrors!
Username/Password: android/android
Feel free to donate to the new hardware fund (donate) if you like my work. It would be greatly appreciated!
Please hit the "Thanks" button if this post helps you out!
Code:
[U][B]Changelog:[/B][/U]
v1 - Initial Release Dec 26, 2013
v1.0.1 - Released Jan 03, 2014
.. Added swap space
.. Increased dynamic drive max to 100 GB
.. Installed latest VirtualBox Guest Additions
.. Updated
.. Optimized
v1.1 - Jan 16, 2014
.. Updated and repackaged OVA file for VMWare
v1.2 - Feb 04, 2014
.. System updated
.. Packaged Manifest for data integrity verification
.. FINAL 13.10 edition (future releases will be based on 14.04)
v1.3 - Feb 08, 2014
.. Revised version numbering because I felt like it
.. Rebuilt with Ubuntu 14.04 base system
.. Increased swap space to 4 gb
.. Increased max disk size to 500 GB
v1.3.1 - Mar 02, 2014
.. Rebuilt from scratch using the latest Xubuntu 14.04 Beta 1 release
.. Testing semi-automated environment script
.. Began torrent distribution
v1.3.2 - Mar 20, 2014
.. Rebuilt from scratch again with new Builduntu Install Disc
.. It's just plain better
v1.4 - Apr 20, 2014
.. Rebuilt using Xubuntu 14.04 LTS Official Release base (via Builduntu Install Disc)
.. Added Guake drop-down terminal for more efficient command line, check it out!
.. HD space reduced to 250 GB dynamically allocated (was anyone ever getting close to 500 before?)
.. Shared folders should be working now (you can build in a directory on your host system, add the folder via Settings in VirtualBox)
v1.5 - Dec 27, 2014
.. Xubuntu 14.10 base
.. Installed ccache
.. JDK7 for Android L builds
v1.6 - Jul 17, 2015
.. Xubuntu Core 15.04 base
.. Switch to LVM
.. Reduced OVA size (almost 1 GB smaller!)
.. Removed Guake in favor of xterm drop-down. Ctrl-F12 for the terminal hotkey
.. Cleaned up package list
v2.0 - Apr 29, 2016
.. Rebase to Xubuntu 16.04 with Builduntu ISO v2
.. Transition to OpenJDK 8 for Android M builds
Thanks, downloading it...
Wow! Thank you very much! Will try soon! :good:
Sent from my HTC One using XDA Premium 4 mobile app
Giving it a shot
Been oddly having trouble setting up my environment. Your previous post got me further then any other instructions. I'll give this a shot and see if it resolves my problem. Thanks in advance!
So far its working great! Thanks again! :good: :good:
I am on vmware fusion on Mac OSX 10.9.1, can I install your pre configured ubuntu on it?
Edited:
Oracle seems better in this circumstance anyhow. I was able to optimize ram and cpu settings but how to increase virtual drive. Its a PCIe SSD 1TB. I wanted to increase the VM up to 150GB. I did not see any easy way of doing it?
EDITED:
Figured out with some googling and using the cloneHD and ModifyHD tools built into virtual box and using terminal commands. I was able to resize the VWMK. The real tricky part is once that is done you have to resize in Linux because its still 60GB again google search found an easy way using gparted and modifying the /etc/fstab!!
Edited again:
I think the swap file was really set too low. I made it 16GB which is recommend by the source.android site. I know this helped a lot because it was lagging until I changed it.
Hi
Is it ok to export appliance using virtual box and import it from vmware?
Cos i use vmware workstation 10
Jaskaran498 said:
Hi
Is it ok to export appliance using virtual box and import it from vmware?
Cos i use vmware workstation 10
Click to expand...
Click to collapse
You can load it up perfectly fine in vmware :good: did that myself as I prefer vmware myself ^^
Sent from my HTC One using XDA Premium 4 mobile app
not working for me.
that's what i get when i try to import in VMware.
c4cyro said:
not working for me.
that's what i get when i try to import in VMware.
Click to expand...
Click to collapse
I imported the download into VMware workstation with no problems. I didn't try exporting from virtual box nor with VM player although the player should work the same as workstation.. Maybe try importing the original download without messing with virtual box?
Sent from my HTC One using XDA Premium 4 mobile app
i downloaded and just imported into vmware nothing else.
did not work. using the same file on virtual box works okay.
Hmm idk then, like I said, using VMware Workstation 10 I had NO problems importing and running it
Sent from my HTC One using XDA Premium 4 mobile app
Thanks a lot for providing Builduntu, saves alot of trouble
i was wondering..
how much free space do i need to have to get the compiling done? i mean...how much is recommended?
Nice one, thanks!
I think this needs to get a sticky!
Uzayr said:
Thanks a lot for providing Builduntu, saves alot of trouble
i was wondering..
how much free space do i need to have to get the compiling done? i mean...how much is recommended?
Click to expand...
Click to collapse
i also want to know same thing
mor_1228 said:
i also want to know same thing
Click to expand...
Click to collapse
All said and done you're looking at 40-50 Gb.
It's 10 or so for the repo source of your choice and device trees (AOKP, CM, etc.) then the build process itself takes another 30ish. You can "make clobber" in between builds to free up that 30 gig, but any time you compile a ROM it's going to need that space again.
By the way - the virtual hard drive on the VM is dynamically allocated, so it will only expand out the space as it is required. However, it won't "shrink" back down again, even after you delete the files.
sylentprofet said:
All said and done you're looking at 40-50 Gb.
It's 10 or so for the repo source of your choice and device trees (AOKP, CM, etc.) then the build process itself takes another 30ish. You can "make clobber" in between builds to free up that 30 gig, but any time you compile a ROM it's going to need that space again.
By the way - the virtual hard drive on the VM is dynamically allocated, so it will only expand out the space as it is required. However, it won't "shrink" back down again, even after you delete the files.
Click to expand...
Click to collapse
i have one till this step now what to do ?
1. Download and install VirtualBox for your host system from here.
2. Download the latest builduntu zip archive and extract builduntu.ova to your hard drive.
3. Start VB, click File > Import Appliance. Select "Open Appliance" and choose builduntu.ova, then click Next to import the virtual machine.
4. Highlight builduntu in VirtualBox Manager and open Settings. Under "System" you may want to give it more RAM and Processor Cores. The higher these values are, the faster you will compile ROMs.
5. Start the machine, pull up a terminal and initialize a git repo. Once the source is finished downloading, you're ready to go!
now how to get psx rom latest build ? can make tutorial to add or remove or merge features of different roms into 1 ? :highfive:
sylentprofet said:
All said and done you're looking at 40-50 Gb.
It's 10 or so for the repo source of your choice and device trees (AOKP, CM, etc.) then the build process itself takes another 30ish. You can "make clobber" in between builds to free up that 30 gig, but any time you compile a ROM it's going to need that space again.
By the way - the virtual hard drive on the VM is dynamically allocated, so it will only expand out the space as it is required. However, it won't "shrink" back down again, even after you delete the files.
Click to expand...
Click to collapse
i tried the 2.0 build with virtual box. i get to choose whether i need to start ubuntu normally or in recovery..and after i make my choice i'm stuck in a black screen....nothing happens
i'm going to try 2.1 and give it another shot.
When I open terminal and enter su to grant root permission and enter password android, it says Authentication Failure
what is the password in that instance? how do i get root permission?
jblazea50 said:
When I open terminal and enter su to grant root permission and enter password android, it says Authentication Failure
what is the password in that instance? how do i get root permission?
Click to expand...
Click to collapse
yeah su doesnt work but sudo command work well with password android.
i tried to change password but system hang