So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?
It IS Lupus said:
So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?
Click to expand...
Click to collapse
Well... You'll need a vendor tree first. And you'll have to run it on a 64-bit box with 64-bit linux. You have to change 'froyo' to 'gingerbread' in EasyDev, so it will grab CM7 source. There will also be some other differences to work out.
As soon as there's a vendor tree available and I have the time to test, I'll finish up EasyDev v7. Some of the additions that I have actually worked on so far are:
1) two or three bug fixes
2) adding CM7
3) adding option to install tiny or full gapps
The CM6 code has been unstable recently in addition to koush's hosting having issues, so I have had plenty of speed bumps in addition to real life stuff.
So... If you can wait on me, that's fine. If not, go for it! Feel free to post your code changes in the thread. We'll take any help we can get.
gnarlyc said:
And you'll have to run it on a 64-bit box with 64-bit linux.
Click to expand...
Click to collapse
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0
bftb0 said:
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0
Click to expand...
Click to collapse
I honestly wasn't sure, but a quick Google search...
http://groups.google.com/group/android-building/browse_thread/thread/852d63ab6124c87e
This is a post from the Android Building group. It appears to be a JDK issue. I've not really tested either way as of yet, although apparently Google says "use a 64-bit host to build, that's what is supported."
Whenever I try to compile my kernel using the cyanogenmod guide, I get error 1 and error 2 at the end of the compiling process. I'm using codesourcery 2010.09 and I think it's a problem with my toolchain because the cyanogenmod guide looks to use a different ARM EABI toolchain that I can't find. I think my commands are wrong. I'm also on 64-bit Ubuntu, and I heard that 64 can cause problems. Could any of you awesome devs shine some light on this for me?
Sent from my Desire HD using XDA App
If you dont give us the exact error message, we cannot (I repeat CANNOT) help you.
You can try this guide too: http://tjworld.net/wiki/Android/Linux/ARMCrossCompileOnIntel
Ive spent the last week or so ever since samsung released their code, trying to compile ICS on fedora 16, after countless hours downloading and compiling code i finally got it. i wanted to share my results with you guys hopefully it will save others some troubles......
ive been using linux for 20 years, but i'm very very new to android development, and since i'm not allowed to post in the development forum i will post it here its pretty simple
but i did get it all compiled and running on my SGS2 from at&t
i'm not gonna get into the details of downloading the source code, but once you download the source code, and run the envsetup script and the lunch full-eng
follow these steps to build the os..
I untarred the samsung Platform.gz file into the android source directory first.
Some of this info i got from ttp:// rootzwiki.com/topic/8037-compile-android-on-fedora-1516-by-xoomdev/
Then:
1.) Install Packages
yum install -y zip curl gcc gcc-c++ flex bison gperf glibc-devel.{x86_64,i686} zlib-devel.{x86_64,i686} ncurses-devel.i686 libX11-devel.i686 libstdc++.i686 libsx-devel readline-devel.i686 libXrender.i686 libXrandr.i686 schedtool pngcrush
2.) Downgrade make i found release 15 is the only one that works right
yum upgrade make --nogpgcheck --releasever=15
3.) comment out line 136 of build/core/main.mk to stop a java version error
4.) UnComment line 63 of libcore/JavaLibrary.mk
5.) Add LOCAL_LDLIBS+=-lX11 to development/tools/emulator/opengl/host/renderer/Android.mk
6.) Add LOCAL_CFLAGS+=-m32 to to top Level Makefile
7.) make -j16
hope this helps.....
Thanks...I was about to start this. I wonder why the make downgrade, though...I'll check into that.
Sent from my GT-P7500 using XDA Premium HD app
Thanks you!
Is this the 64 bit version or 32 of Fadora? Sorry read your install calls THANK YOU!
Slie said:
Is this the 64 bit version or 32 of Fadora? Sorry read your install calls THANK YOU!
Click to expand...
Click to collapse
as i know android compile only on 64 bit
I'm trying to compile Omni on a 32 bit Linux system, using the procedure given here: http://docs.omnirom.org/Build_for_i9300. However, the binaries in the directory
~/android/omni/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7/bin/
are 64 bit binaries, and I have a 32 bit system. Are these binaries available in 32 bit versions? And if so, how do I download them into my ~/android/omni directory?
Thanks!
AFAIK you cannot compile Android on 32-bit systems.
chasmodo said:
AFAIK you cannot compile Android on 32-bit systems.
Click to expand...
Click to collapse
32 bit systems have not been supported as a build host by Android for a LONG time.
Drat! Oh well... my options for compiling my own mods will have to wait until I either upgrade my system (dunno even if a have a 64-bit chip), or my computer.
Thanks for your replies.
amca1960 said:
Drat! Oh well... my options for compiling my own mods will have to wait until I either upgrade my system (dunno even if a have a 64-bit chip), or my computer.
Click to expand...
Click to collapse
Hi, I struggled with this a year ago and managed to set up a 4.6 compiler for a 32bit machine to build cyanogenmod using
Code:
https://github.com/yath/android_prebuilts_gcc_linux-x86-32_arm_arm-linux-androideabi-4.6
Its not 4.7, and as stated above, its not supported. It worked ok for me for jellybean but not tried it recently as I have a 64bit machine now.
Here is a complete tutorial about:Android Kernel(compile)+ Linaro/Sabermod/NDK.
//In the future I will add a tutorial related to undervolt., overclock, cpu governor, and others.(only Snapdragon CPU)
Kernel Features HERE
Youtube channel(if you have troubles).
Part 1: vmware+ubuntu+Installing the required files:
Linaro
Part 2: download kernel source files+ setup toolchain+jdk+abootimg
Part 3: kernel+ boot.img file
Part 4: test
Part 2/3 SABERMOD
Part 2/3 Android NDK
More:
extract .config via ADB:
compile-speed:
dump boot.img:
Change bootimg.cfg size-hex:
Create boot.img via script.sh. Much faster!!!
Linaro vs NDK:
I'll keep you updated, so stay tuned
Reserved
Thank you so much for this guide! before people had to learn from strictly written ones and it was difficult for a lot of us to pick up
oh and congrats on Portal feature!
Thank you for this guide . I can wait to try it .
Sent from my GT-I9100G using XDA Premium 4 mobile app
Sorry if its already been answered but can I use Ubuntu 14.04 to do this? what advantage does 12.04 have?
You can use either Ubuntu 14. However this does not affect anything(about kernel). But I preferred the version 12 because it is more popular, and if problems "arise", it's easier to find solutions.
!
great tutorials! any chnce of one compiling with GCC?
also man! YOUR COMPUTE IS ON STEROIDS!!!
Maybe, but in summer(I'm still busy with school). GCC needs to be changed in Part II.
also man! YOUR COMPUTE IS ON STEROIDS!!!
Click to expand...
Click to collapse
Configuration is:
Asus k53sv
-Intel Core I7 2630QM
-12 GB Ram (1333 mhz cl9)
-HDD: 750GB WD Black;
-GPU Intel HD 3000+Nvidia GT540M 2gb ddr3;
+1080p tv(monitor) but only for tutorials.
srsdani said:
Maybe, but in summer(I'm still busy with school). GCC needs to be changed in Part II.
Configuration is:
Asus k53sv
-Intel Core I7 2630QM
-12 GB Ram (1333 mhz cl9)
-HDD: 750GB WD Black;
-GPU Intel HD 3000+Nvidia GT540M 2gb ddr3;
+1080p tv(monitor) but only for tutorials.
Click to expand...
Click to collapse
yeah ive been having problems with GCC on ubuntu 14.04, on my last installation(also 14.04) all compiled fine, yet this fresh installation theres no errors but doesnt boot(stock unmodified sources) :/
What's your device? Some have a slightly different configuration(Samsung or Sony/Sony Ericsson etc.).
srsdani said:
What's your device? Some have a slightly different configuration(Samsung or Sony/Sony Ericsson etc.).
Click to expand...
Click to collapse
after days of troubleshooting i finally just found the problem..
i had exported PATH to JDK 8 in my .bashrc, i just compiled and it worked
thanks to your video making me look in .bashrc!
LEGEND!!!!
Ricky Divjakovski said:
after days of troubleshooting i finally just found the problem..
i had exported PATH to JDK 8 in my .bashrc, i just compiled and it worked
thanks to your video making me look in .bashrc!
LEGEND!!!!
Click to expand...
Click to collapse
Can this work for my s4 I9506 stock kernel
Kind of over complicated?
No need to modify .bashrc to build kernels, also nautilus-open-terminal, and synaptic arent needed in any way for kernel compilation and its kinda bad practice to auto accept with sudo apt-get install -y.
Also I dont think java is needed to build kernels (since they are mostly C and assembly code), but oracle java 6 is usually what is recommended for android builds.
Basically all you really need to do is install the required packages, download kernel source and desired toolchain, then run these lines in terminal to get your zImage-
export ARCH=arm
export CROSS_COMPILE= <directory to toolchain>
make <your kernel default config>
make -j<number of threads>
That way makes it much easier to try out different toolchains and toolchain versions
Buddy, mention clearly of which device u r using, n on which device it will work.:laugh: by the way nice work
Niku-Droid said:
Buddy, mention clearly of which device u r using, n on which device it will work.:laugh: by the way nice work
Click to expand...
Click to collapse
kernel building for different devices is pretty much all the same, all that differs is the kernel source, defconfig and sometimes a few extra commits to work with linaro toolchain. And if you use the arch specific toolchains you need to pick the right one for your device
metalspring said:
kernel building for different devices is pretty much all the same, all that differs is the kernel source, defconfig and sometimes a few extra commits to work with linaro toolchain. And if you use the arch specific toolchains you need to pick the right one for your device
Click to expand...
Click to collapse
Yea, buddy, but he should mention about which device is he using, so it would give us a brief idea, that what we have to do.
Niku-Droid said:
Yea, buddy, but he should mention about which device is he using, so it would give us a brief idea, that what we have to do.
Click to expand...
Click to collapse
Device: Acer Cloudmobile s500
Cpu snapdragon s4 krait dual—core 1.5 ghz
Gpu Adreno 225;
1gb ram
8 mp camera+1.9 mb front;
1460 mah battery
Hd 720p display
Very nice tutorial. I just got into building from source. Yesterday shortly before you posted this, I have successfully compiled a ROM for the first time. Also can you add the link to the other tutorial when it's done on this thread?
can anyone just post the video links they are not opening on my mobile , are they on YouTube so I can DL them for future reference
Thanks
Look great will be looking into tutorials