Hi all,
Found cyanogen source code a great one to start playing with Android and I have compiled the source code. The compiled ROM is working perfectly in my N1. Then I decided to start working with Eclipse. I copied .classpath file from development/ide/eclipse to root directory of the source code and created a new Java project from existing source in Eclipse. Thing ended up with an error about build path:
Code:
The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Enum. Fix the build path then try building this project
Does anyone know how to fix this error?
Related
Dev's,
This is for those of you that build ROM's from source code and have forked repo's from the main line so you can make changes for your specific device i.e. android_framworks_base. These mini scripts will allow for the following
1. Download your local repo's and add a git remote back to the fork so you can fetch the updated head's
2. Fetch the heads as you see fit
3. Copy the updated source into your local source build folder after a $repo sync
4. Push back up the changes after the ROM has been tested
There is full set of instructions at the following location.
https://github.com/g60madman/repo_update_tool
These mini scripts can be edited for all flavors of source code be it AOSP, AOKP, CM, or whatever; along with any repo structure github, google, bitbucket etc..
Enjoy!
I'm completely new to developing and this is my first Android project and also my first time using Github (or any other vcs). I've found guides for how to import projects from Github into Android Studio, but I can't figure out how to upload a new project to Github. I've created a basic project with Android Studio and I've installed git for Windows and openssh in cygwin, but not sure where to go from here. Any help would be great.
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
christi9503 said:
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
Click to expand...
Click to collapse
Please help!
christi9503 said:
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
Click to expand...
Click to collapse
One question. You have the bootloader unlock? you as unlock the bootloader? Sorry for my bad English and greetings from Mexico.
Enviado desde mi LG-P714 mediante Tapatalk
neutrondev said:
Hello!
I am trying to port some Custom ROM to my Lg P710 (Lg L7 II). Since the bootloader got unlocked and now i have CWM i decided to start to port a custom rom. I read some tutorials and i understood the basics but how can i get the stock rom from Lg. I downloaded the Kdz file and tried to build from source but i am stuck here. I don't know what i shall do. When i build from source i get a really small output like e 30 MB output. Can someone help me clarify this please?
Lg Instructions for building android and kernel:
1. Android build
- Download original android source code ( Jelly Bean 4.1 ) from http://source.android.com
- Unzip opensource packages of P710(Optimus L7 II)_Android_JB_P710V10h_EUR.zip into downloaded android source directory
- And, merge the source into the android source code(Jelly Bean)
- Run following scripts to build android
a) source build/envsetup.sh
b) choosecombo
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain)
into the android folder
( add prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin to PATH )
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Unzip using following command at the android folder
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain)
into the android folder.
- cd kernel
- export ARCH=arm
- export TARGET_PRODUCT=vee7e_open_eu
- export CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make vee7-rev_10_defconfig
- make zImage
3. After Build, You Can find the build image at arch/arm/boot.
Click to expand...
Click to collapse
Which Rom are u BUILDING?
All guides are here -> http://forum.xda-developers.com/showthread.php?t=2073370
WiFi direct has a shell tool for doing configuration changes called "p2p_cli". I can't find a newer version compiled to run on Android 5.0 with the new PIE security requirement.
It seems to be part of the Android platform source code, here: https://android.googlesource.com/platform/external/wpa_supplicant_8/+/master/src/p2p
Reference on PIE compile:
http://stackoverflow.com/questions/...id-l-error-only-position-independent-executab
Some ROM developer can maybe compile it for me and provide a download of the binary? Thank you.
Whilst compiling Cyanogenmod I got this error:
Code:
ccache: FATAL: Could not find compiler "arm-eabi-gcc" in PATH.
Based on the manifest
https://github.com/LineageOS/android/blob/cm-12.1/default.xml#L542
the compiler is platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
from
https://android.googlesource.com/pl...inux-x86/arm/arm-eabi-4.8/+/android-5.1.1_r37
If I add that full path to my PATH variable I can compile the ROM successfully.
However, that seems wrong to me.
The compiler is already part of the source tree.
Shouldn't something in one of the make files or build scripts be setting this rather than me setting it manually?
Note: I am not using a custom toolchain, it is the standard one from aosp.
opticyclic said:
Whilst compiling Cyanogenmod I got this error:
Code:
ccache: FATAL: Could not find compiler "arm-eabi-gcc" in PATH.
Based on the manifest
https://github.com/LineageOS/android/blob/cm-12.1/default.xml#L542
the compiler is platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
from
https://android.googlesource.com/pl...inux-x86/arm/arm-eabi-4.8/+/android-5.1.1_r37
If I add that full path to my PATH variable I can compile the ROM successfully.
However, that seems wrong to me.
The compiler is already part of the source tree.
Shouldn't something in one of the make files or build scripts be setting this rather than me setting it manually?
Note: I am not using a custom toolchain, it is the standard one from aosp.
Click to expand...
Click to collapse
Toolchains aren't automatically set, at least for now. Possible causes being...
There are multiple versions of Toolchain that are synced together, and it isn't necessary that the newer version of the same toolchain "must" compile the code with success, which was properly compiled by an older version.
Also, by this, the developer has complete freedom to change the ROM/Kernel toolchain.
Coming to the Question in Thread Title, If you're building a ROM, then toolchain has to be added in PATH
Arvind7352 said:
Toolchains aren't automatically set, at least for now. Possible causes being...
There are multiple versions of Toolchain that are synced together, and it isn't necessary that the newer version of the same toolchain "must" compile the code with success, which was properly compiled by an older version.
Also, by this, the developer has complete freedom to change the ROM/Kernel toolchain.
Coming to the Question in Thread Title, If you're building a ROM, then toolchain has to be added in PATH
Click to expand...
Click to collapse
Thanks for clarifying.
Ideally it should scan the source tree for the compiler by default so it has something to fall back to in case a custom one is not specified.
What confused me is that I don't see this nugget of information specified in any of the guides I read about compiling ROMs.