Jean-Baptiste Queru Join group to reply
6:56 PM (1 hour ago)
We're releasing Android 4.1 in AOSP today.
The name of the tagged release is android-4.1.1_r1.
The name of the development branch is jb-dev.
We recommend that you create new clients, even if you're working in
the master branch. It'll make your clients smaller and faster to sync.
Proprietary binaries are available for Nexus 7 and Galaxy Nexus. Nexus
S and Xoom will follow.
JBQ, on behalf of the entire Android team at Google.
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
I'm looking forward to Jelly Bean on the Xoom. I've been enjoying it on the GNex
PacerguyDon said:
I'm looking forward to Jelly Bean on the Xoom. I've been enjoying it on the GNex
Click to expand...
Click to collapse
I can't wait... my xoom is impatiently waiting! (and my sgs3 lol)
speculation puts release date maybe a week away.
My xoom and gs3 is waiting...
I have already downloaded the source from the repo and it has a debug version available for the wifi xoom.....
It ended up bombing out :/ not sure whats missing
[email protected]:~/jelly_bean_source# make -j32
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=full_wingray
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-2.6.32-31-server-x86_64-with-Ubuntu-10.04-lucid
HOST_BUILD_TYPE=release
BUILD_ID=JRO03C
OUT_DIR=out
============================================
find: `src': No such file or directory
build/core/base_rules.mk:171: *** system/abi/cpp: MODULE.TARGET.SHARED_LIBRARIES.libgabi++ already defined by abi/cpp. Stop.
Since the Nexus S 4G and Verizon Galaxy Nexus are supported in AOSP with official binaries again, I'm hopeful we may see the Verizon Xoom supported in AOSP once again as well.
Sent from my Galaxy Nexus using Tapatalk 2
Syncing It now, I've got the full aosp mirrored ... There's memory leak with the linux version of python/repo (not sure which) Got to reboot between sync and build otherwise I end up in swap, with 16gigs. lol
then
Code:
time make -j16
Because I'm a stats geek.
jnc8651 said:
I have already downloaded the source from the repo and it has a debug version available for the wifi xoom.....
It ended up bombing out :/ not sure whats missing
[email protected]:~/jelly_bean_source# make -j32
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=full_wingray
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-2.6.32-31-server-x86_64-with-Ubuntu-10.04-lucid
HOST_BUILD_TYPE=release
BUILD_ID=JRO03C
OUT_DIR=out
============================================
find: `src': No such file or directory
build/core/base_rules.mk:171: *** system/abi/cpp: MODULE.TARGET.SHARED_LIBRARIES.libgabi++ already defined by abi/cpp. Stop.
Click to expand...
Click to collapse
I got the 'src' not found but It just carried on.
Check this Google Groups Post Out see if it helps
I am compiling Jelly Bean for my Milestone 2.
I get this error and can not fix it.
Code:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=full_milestone2
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-23-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JRO03C
OUT_DIR=out
============================================
build/core/base_rules.mk:79: *** Module name: 01_Vendor_ti_omx
build/core/base_rules.mk:80: *** Makefile location: hardware/ti/omap3/omx/core_plugin
build/core/base_rules.mk:81: *
build/core/base_rules.mk:82: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:83: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:84: *
build/core/base_rules.mk:85: * optional, debug, eng, tests, samples
build/core/base_rules.mk:86: *
build/core/base_rules.mk:87: * If the module is expected to be in all builds
build/core/base_rules.mk:88: * of a product, then it should use the
build/core/base_rules.mk:89: * "optional" tag:
build/core/base_rules.mk:90: *
build/core/base_rules.mk:91: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:92: * Android.mk for the affected module, and add
build/core/base_rules.mk:93: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:94: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:95: * makefile(s) where it's necessary, if
build/core/base_rules.mk:96: * appropriate.
build/core/base_rules.mk:97: *
build/core/base_rules.mk:98: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:99: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:100: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:101: * build/target/product/core.mk
build/core/base_rules.mk:102: *
build/core/base_rules.mk:103: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.
I have added the module to Core.mk and the optional thing to the Android.mk but that does not fix it.
Any help is appreciated.
p0isonra1n said:
I am compiling Jelly Bean for my Milestone 2.
I get this error and can not fix it.
Code:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=full_milestone2
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-23-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JRO03C
OUT_DIR=out
============================================
build/core/base_rules.mk:79: *** Module name: 01_Vendor_ti_omx
build/core/base_rules.mk:80: *** Makefile location: hardware/ti/omap3/omx/core_plugin
build/core/base_rules.mk:81: *
build/core/base_rules.mk:82: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:83: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:84: *
build/core/base_rules.mk:85: * optional, debug, eng, tests, samples
build/core/base_rules.mk:86: *
build/core/base_rules.mk:87: * If the module is expected to be in all builds
build/core/base_rules.mk:88: * of a product, then it should use the
build/core/base_rules.mk:89: * "optional" tag:
build/core/base_rules.mk:90: *
build/core/base_rules.mk:91: * Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:92: * Android.mk for the affected module, and add
build/core/base_rules.mk:93: * the LOCAL_MODULE value for that component
build/core/base_rules.mk:94: * into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:95: * makefile(s) where it's necessary, if
build/core/base_rules.mk:96: * appropriate.
build/core/base_rules.mk:97: *
build/core/base_rules.mk:98: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:99: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:100: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:101: * build/target/product/core.mk
build/core/base_rules.mk:102: *
build/core/base_rules.mk:103: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.
I have added the module to Core.mk and the optional thing to the Android.mk but that does not fix it.
Any help is appreciated.
Click to expand...
Click to collapse
Think maybe this might help you http://forum.xda-developers.com/showthread.php?t=1071833
Nope
It didn't help because the module I have the error with has no user tags and its the last thing stopping me compiling.
May be you should try contacting Quarx, his bringing JB to Defy...
Sent from my MotoA953
I Will
Megalith27 said:
May be you should try contacting Quarx, his bringing JB to Defy...
Sent from my MotoA953
Click to expand...
Click to collapse
I'll try contacting him.
hello folks!
i have been working on kernels for various xperia devices since the Xperia X10... i will update this thread with information on how to build kernels for various xperia devices...
Sony (Ericsson) started off helping the developer community with information on how to build kernels:
http://developer.sonymobile.com/2011/05/06/how-to-build-a-linux-kernel/
do read the above post, though its slightly old (2011), its really good! Since then Sony has released various devices which use a variety of chipsets and each chipset has different ways to build bootable kernel...
the objective of this thread is to provide brief instructions for some of these chipsets across the various device generations to build bootable kernels...
this will not cover how to build working ramdisks... you can always use the stock ramdisks from kernel.sin... here is how to get stock ramdisk out from kernel.sin...
Toolchains:
I have tested various toolchains for building kernels and very few work correctly on the kernel sources to get bootable kernel.
The toolchains which worked for me are:
arm-eabi-4.4.3 - GCC 4.4.3 toolchain from CyanogenMod repo
arm-eabi-linaro-4.6.2 - GCC Linaro 4.6.2 (2011.10) toolchain
arm-linux-androideabi-4.7 - GCC 4.7 from Google repo
all of these are posted on my git repo:
https://github.com/DooMLoRD/android_prebuilt_toolchains
sometimes the kernel sources need to be modified slightly to support compiling using these toolchains. I have mentioned the necessary patches where-ever applicable.
Instructions for various generation of devices:
Xperia 2014 (H1) - msm8974ab - Xperia Z2
Xperia 2013 (H2) - msm8974 - Xperia Z1, Z Ultra, Z Ultra GPe, Z1 Compact
Xperia 2013 (H1) - apq8064 - Xperia Z, ZL, ZR, Tablet Z
Xperia 2013 (H1) - msm8960t - Xperia SP
Xperia 2012 (H2) - msm8960 - Xperia T, TX, V
Xperia 2012 (H1) - msm8660 - Xperia S, SL, Ion, Acro S
Xperia 2011 - msm8x55/msm7x30 - Xperia Arc, Play, Neo, Ray, etc
reserved for later
Instructions for MSM8x55/MSM7x30
Latest sources available at:
http://developer.sonymobile.com/dow...ves/open-source-archive-for-build-4-1-b-1-13/
Recommended toolchain:
GCC 4.6 Linaro
Fix Makefile for 4.6 Toolchain:
Code:
KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-Werror \
to:
Code:
KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \
-Wno-unused-but-set-variable -Wno-uninitialized \
Supported boards on this platform:
zeus - Xperia Play, Xperia L
mogami - Xperia Arc, Arc S, Ray, Neo, etc
Building kernel (zImage):
for Xperia Arc (anzu):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make semc_anzu_defconfig
for Xperia Play (zeus):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make semc_zeus_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make -j8
Instructions for building boot.img
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/tree/master/msm7x30_mogami_zeus
Sony used the standard boot.img format for this chipset devices
building boot.img
use the following command:
Code:
./mkbootimg --base 0x00200000 --kernel zImage --ramdisk ramdisk.cpio.gz -o boot.img
Special notes
Sometimes the compiled kernel will just not boot, will show blank screen. Workaround is, ramdisks needs to be filled with filler so that total size is bigger.
boot.img can be hotbooted (fastboot boot boot.img)
regards,
DooMLoRD
Novathor?
Instructions for MSM8260/MSM8660
Latest sources available at:
Since I actively develop for a device of this platform (Xperia S) latest sources can found at my git repo:
https://github.com/DooMLoRD/android_kernel_sony_msm8660/tree/sony_sources
Recommended toolchain:
GCC 4.7
Fixes for 4.7 Toolchain:
Makefile fix
defconfig fix
Supported boards on this platform:
fuji- Xperia S, SL, Ion, Acro S
Building kernel (zImage):
for Xperia S (nozomi):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make fuji_nozomi_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8
Instructions for building kernel.elf
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/tree/master/msm8660_fuji
Sony shifted to ELF format for this chipset...
They had posted instructions on there website:
http://developer.sonymobile.com/201...-archive-released-with-building-instructions/
(avoid using those files as they are for GingerBread)
building kernel.elf
use the following command (for JB):
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm
the additional files required are posted at my build tools repo
Special notes
RPM is different for each device and also differs for OS release, so the same RPM wont work on Xperia S or Xperia Ion and GB/ICS/JB each have different RPMs
kernel.elf CANNOT be hotbooted (fastboot boot kernel.elf)
regards,
DooMLoRD
Instructions for MSM8960
Latest sources available at:
Since I actively develop for a device of this platform (Xperia T) latest sources can found at my git repo:
https://github.com/DooMLoRD/android_kernel_sony_msm8960/tree/sony_sources
Recommended toolchain:
GCC 4.6 Linaro
Supported boards on this platform:
blue- Xperia T, TX, V
Building kernel (zImage):
for Xperia T (mint):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make blue_mint_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make -j8
Instructions for building kernel.elf
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/tree/master/msm8960_blue
Sony uses ELF format for this chipset...
building kernel.elf
use the following command (for JB):
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
the additional files required are posted at my build tools repo
Special notes
RPM is different for each device and also differs for OS release, so the same RPM wont work on Xperia T or Xperia V as each have different RPMs
kernel.elf CANNOT be hotbooted (fastboot boot kernel.elf)
regards,
DooMLoRD
Instructions for MSM8960T
Latest sources available at:
Since I actively develop for a device of this platform (Xperia SP) latest sources can found at my git repo:
https://github.com/DooMLoRD/android_kernel_sony_msm8960t/tree/sony_sources
Recommended toolchain:
GCC 4.7
Fixes for 4.7 Toolchain:
Makefile fix
Supported boards on this platform:
viskan- Xperia SP
Building kernel (zImage):
for Xperia SP (huashan):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make viskan_huashan_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8
incase u get errors like:
Code:
error : /scripts/gcc-wrapper.py
just correct the permissions of that file
Code:
chmod 755 ./scripts/gcc-wrapper.py
Instructions for building kernel.elf
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/tree/master/msm8960t_viskan
Sony uses ELF format for this chipset...
building kernel.elf
use the following command:
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
the additional files required are posted at my build tools repo
Special notes
kernel.elf CANNOT be hotbooted (fastboot boot kernel.elf)
regards,
DooMLoRD
Instructions for APQ8064
Latest sources available at:
Since I actively develop for a device of this platform (Xperia Z) latest sources can found at my git repo:
https://github.com/DooMLoRD/android_kernel_sony_apq8064/tree/sony_sources
Recommended toolchain:
GCC 4.7
Fixes for 4.7 Toolchain:
Makefile fix
prima fix
Supported boards on this platform:
fusion3- Xperia Z, ZL, Tablet Z, ZR
Building kernel (zImage):
for Xperia Z (yuga):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make fusion3_yuga_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8
Instructions for building boot.img
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/blob/master/apq8064_fusion3
Sony uses slightly different boot.img format for this chipset...
building boot.img
use the following command:
Code:
./mkbootimg --base 0x80200000 --kernel zImage --ramdisk_offset 0x02000000 --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=400M androidboot.emmc=true" --ramdisk ramdisk.cpio.gz -o boot.img
corrected build tools are posted at my build tools repo
Special notes
boot.img CANNOT be hotbooted (fastboot boot boot.img)
regards,
DooMLoRD
Instructions for MSM8974
Latest sources available at:
I will soon be getting the Xperia Z1 and actively develop for it... i will keep the latest sources at my git repo:
https://github.com/DooMLoRD/android_kernel_sony_msm8974/commits/sony_sources
Recommended toolchain:
GCC 4.6
Fixes for 4.6 Toolchain:
Makefile fix 1
Makefile fix 2
Supported boards on this platform:
rhine- Xperia Z1, Z Ultra
Building kernel (zImage):
for Xperia Z1 (honami):
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make rhine_honami_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/android-toolchain-eabi-linaro-4.6-2011.10/bin/arm-eabi- make -j8
Instructions for building boot.img
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/blob/master/msm8974_rhine
Sony uses slightly different boot.img format for this chipset...
building boot.img
krabappel2548 said:
MSM8974 needs something new to build a kernel, this is called a dt.img. This basically is an img file which holds information about the board pagesize, kernel version and some other kernel related things. You can only use a specific dt.img with a kernel, this file needs to be generated by a binary called dtbTool. This binary can be found in the Cyanogen repo's or you can download a prebuild one in this thread.
Click to expand...
Click to collapse
to get the dt.img:
Code:
# path to kernel sources
KERNEL_SRC_PATH=~/android_kernel_sony_msm8974/
echo "generating device tree..."
./dtbTool -o dt.img -s 2048 -p {KERNEL_SRC_PATH}/scripts/dtc/ {KERNEL_SRC_PATH}/arch/arm/boot/
once u have the dt.img along with the zImage and ramdisk.cpio.gz use the following command:
Code:
./mkbootimg --base 0x00000000 --kernel zImage --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 msm_rtb.enable=0 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y" --ramdisk ramdisk.cpio.gz --dt dt.img -o boot.img
corrected build tools are posted at my build tools repo
Special notes
boot.img CAN be hotbooted (fastboot boot boot.img)
regards,
DooMLoRD
XperianPro said:
Novathor?
Click to expand...
Click to collapse
Later I will add info for them too....
Hello doom,I want to ask you something.I manage to port your doomkernel v22 GB for Arc/Arc S to Neo/Neo V and I want permissions from you to share it in Neo forum.Sorry for asking here, but you don't answer me on the PM that I send you.
Sorry for my English.
Sent from my Xperia Neo V using xda app-developers app
it is possible port the kernel of 'xperia sp on xiaomi mi2a?
the two terminals have the same hardware
updated instructions for MSM8974 kernels
DooMLoRD said:
updated instructions for MSM8974 kernels
Click to expand...
Click to collapse
Please take a look at novathor devices if you have time
Hi sir can you recommend a toolchain for msm7627a (Xperia J) the ones on your github won't work.
Diego910 said:
Please take a look at novathor devices if you have time
Click to expand...
Click to collapse
You need to patch Makefile somethings to disable some flags for these toolchains
Sent from my C6902 using xda app-developers app
@OP
How can I attach my compiled zImage to CM10 build from source? I have already compiled kernel from source and now I want to use it in my CM10 build
Great TUT
Sent from my E15i using xda premium
Great tutorial! But I came across a problem:when compiling a CM kernel for Xperia TX,I need to change the command from
Code:
python mkelf.py -o kernel.elf [email protected] [email protected][COLOR="red"]4[/COLOR]00000,ramdisk [email protected],rpm [email protected],cmdline
to
Code:
python mkelf.py -o kernel.elf [email protected] [email protected][COLOR="red"]7[/COLOR]00000,ramdisk [email protected],rpm [email protected],cmdline
Otherwise the phone won't boot.Only black screen with backlight on and then reboot after pressing the power button,even no Sony/CM logo.
(Another strange case:when I use sksplit to split the official kernel,the ramdisk does lay in 0x81400000.But if I import the hayabusa_defconfig,compile the kernel from Sony source without any change and mkelf with official [email protected],the phone still refuses to boot.I have to change the 4 to 7 to make this kernel boot.Why?)
{MIRO/TIPO/J/E} Addresses
zImage --0x00208000
ramdisk --0x01400000
bootcmd --cmdline
i.e.
python mkelf.py -o boot.img [email protected] [email protected],ramdisk [email protected]
I tried to compile a AOSP based rom, but after
source build/envsetup.sh
like I do with Cm based roms
brunch is not available.
is brunch CM specific and if so what other command do I need with aosp sources?
DavidXanatos said:
I tried to compile a AOSP based rom, but after
source build/envsetup.sh
like I do with Cm based roms
brunch is not available.
is brunch CM specific and if so what other command do I need with aosp sources?
Click to expand...
Click to collapse
What is the AOSP-based ROM that you're trying to build?
Sent from my GT-S7580 using Tapatalk
it was this rom: http://forum.xda-developers.com/optimus-4x-hd/orig-development/dev-aosp-lollipop-5-0-2-t2995695
and thats the set of cammands with which it builds under bbq linux
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r29
#add local manifest
repo sync
# apply cm 12.1 fixes ld 43 and timeconst
cd /devices/lge/p880/patches
bash ./install.sh
cd ../../../..
source build/envsetup.sh
lunch
#selech p880
# to prevent api error:
make update-api
make -j8
make -j8 otapackage
DavidXanatos said:
it was this rom: http://forum.xda-developers.com/optimus-4x-hd/orig-development/dev-aosp-lollipop-5-0-2-t2995695
and thats the set of cammands with which it builds under bbq linux
Code:
repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r29
#add local manifest
repo sync
# apply cm 12.1 fixes ld 43 and timeconst
cd /devices/lge/p880/patches
bash ./install.sh
cd ../../../..
source build/envsetup.sh
lunch
#selech p880
# to prevent api error:
make update-api
make -j8
make -j8 otapackage
Click to expand...
Click to collapse
Then use
Code:
lunch p880
make -j$(cat /proc/cpuinfo | grep "^processor" | wc -l) otapackage
instead of
Code:
brunch p880
Sent from my GT-S7580 using Tapatalk