Hi all,
I used the device, hardware, and kernel trees as given in the pastebin link in the legacy-xperia github
After applying munjeni's patches, I tried to compile. I got this error.
bootable/recovery/ui.c: In function 'update_leds':
bootable/recovery/ui.c:768:42: error: 'RED_LED_FILE' undeclared (first use in this function)
bootable/recovery/ui.c:768:42: note: each undeclared identifier is reported only once for each function it appears in
bootable/recovery/ui.c:769:42: error: 'GREEN_LED_FILE' undeclared (first use in this function)
make: *** [/home/fadhil/android/pac/out/target/product/nypon/obj/EXECUTABLES/recovery_intermediates/ui.o] Error 1
Click to expand...
Click to collapse
From what I saw in ui.c, the affected section is telling the colour of the charging led to change from red to green when battery level increases above 90%.
How do I resolve this error?
I think I have found the reason for the error. When the patches were applied, they produced errors.
What is the cause of this? Does another working set of patches exist?
MuffinIsCute said:
I think I have found the reason for the error. When the patches were applied, they produced errors.
What is the cause of this? Does another working set of patches exist?
Click to expand...
Click to collapse
see here
https://github.com/munjeni/android_hardware_semc/blob/master/patches/bootable_recovery.patch#L30
this is the line causing problem.
alwaysadeel said:
see here
https://github.com/munjeni/android_hardware_semc/blob/master/patches/bootable_recovery.patch#L30
this is the line causing problem.
Click to expand...
Click to collapse
You mean it should be changed to pac_nypon?
One more question here: I tried to use the device hardware and kernel trees from the aosx project instead. However, it was unable to compile as the file cm.mk was missing. Is it alright to just copy the cm.mk file over from the sources suggested in percy's pastebin? Or do I have to modify it to point somewhere else?
MuffinIsCute said:
You mean it should be changed to pac_nypon?
One more question here: I tried to use the device hardware and kernel trees from the aosx project instead. However, it was unable to compile as the file cm.mk was missing. Is it alright to just copy the cm.mk file over from the sources suggested in percy's pastebin? Or do I have to modify it to point somewhere else?
Click to expand...
Click to collapse
xperiaste github is already setup to build cm, it uses aosx trees. use it!
github.com/XperiaSTE
Sent from my Nexus 7
Cherrypick this- https://github.com/XperiaSTE/androi...mmit/bf7216061b2da51c18ecbe4d8f980e8a7c85be01
Cheers,
AJ
Abhinav2 said:
Cherrypick this- https://github.com/XperiaSTE/androi...mmit/bf7216061b2da51c18ecbe4d8f980e8a7c85be01
Cheers,
AJ
Click to expand...
Click to collapse
Stupid question here: How do I cherry pick?
Never mind. I'm still wondering why the change got reverted.
alwaysadeel: You're a lifesaver. I didn't know that XperiaSTE existed. Here's a thank you.
MuffinIsCute said:
Stupid question here: How do I cherry pick?
Never mind. I'm still wondering why the change got reverted.
Click to expand...
Click to collapse
Because when I was part of that team, I told i4g to do that since we were testing something.
AJ
Abhinav2 said:
Because when I was part of that team, I told i4g to do that since we were testing something.
AJ
Click to expand...
Click to collapse
Noob question: The only trees needed are the nypon, the montblanc, the kernel and hardware sources and the vendor tree right? Is that correct?
MuffinIsCute said:
Noob question: The only trees needed are the nypon, the montblanc, the kernel and hardware sources and the vendor tree right? Is that correct?
Click to expand...
Click to collapse
Yeah, more or less.
Cheers,
AJ
Abhinav2 said:
Yeah, more or less.
Cheers,
AJ
Click to expand...
Click to collapse
I tried compiling with the XperiaSTE trees and got this error
[email protected]:~/android/zz$ ./build-pac.sh nypon
No external out, using default (/home/fadhil/android/zz/out)
./build-pac.sh: command substitution: line 117: syntax error near unexpected token `fi'
./build-pac.sh: command substitution: line 117: `shellif[-s~/PACname];thencat~/PACname;elseecho"Beta-1.0";fi)'
Building P A C v..
Looking for PAC product dependencies
Check for XperiaSTE/android_device_sony_nypon in local_manifest
XperiaSTE/android_device_sony_nypon already in local_manifest
Check for XperiaSTE/android_device_sony_montblanc-common in local_manifest
XperiaSTE/android_device_sony_montblanc-common already in local_manifest
Check for XperiaSTE/android_kernel_sony_u8500 in local_manifest
XperiaSTE/android_kernel_sony_u8500 already in local_manifest
Check for XperiaSTE/android_hardware_ste-sony in local_manifest
XperiaSTE/android_hardware_ste-sony already in local_manifest
Check for XperiaSTE/android_vendor_sony in local_manifest
XperiaSTE/android_vendor_sony already in local_manifest
Downloading prebuilts
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 178 100 178 0 0 456 0 --:--:-- --:--:-- --:--:-- 656
100 502k 100 502k 0 0 413k 0 0:00:01 0:00:01 --:--:-- 413k
Archive: vendor/cm/proprietary/Term.apk
inflating: vendor/cm/proprietary/lib/armeabi/libjackpal-androidterm4.so
inflating: vendor/cm/proprietary/lib/mips/libjackpal-androidterm4.so
inflating: vendor/cm/proprietary/lib/x86/libjackpal-androidterm4.so
Setting up environment
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/goldfish/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/sony/nypon/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pac/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/bash_completion/git.bash
including vendor/cm/bash_completion/repo.bash
Lunching device
Looking for dependencies
Dependencies file not found, bailing out.
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=11-20140606-UNOFFICIAL-nypon
TARGET_PRODUCT=pac_nypon
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.8.0-41-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=KVT49L
OUT_DIR=/home/fadhil/android/zz/out
============================================
Starting compilation
Using the default GCC Optimization Level, O2
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=11-20140606-UNOFFICIAL-nypon
TARGET_PRODUCT=pac_nypon
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.8.0-41-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=KVT49L
OUT_DIR=/home/fadhil/android/zz/out
============================================
Checking build tools versions...
/home/fadhil/android/zz/out/target/product/nypon/obj/APPS/SignatureTest_intermediates
external/chromium_org/GypAndroid.linux-arm.mk:109: external/chromium_org/third_party/WebKit/Source/bindings/bindings_sources.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:120: external/chromium_org/third_party/WebKit/Source/core/make_core_derived_sources.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:135: external/chromium_org/third_party/WebKit/Source/devtools/concatenated_devtools_layers_js.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:147: external/chromium_org/third_party/WebKit/Source/heap/blink_heap.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:148: external/chromium_org/third_party/WebKit/Source/heap/blink_heap_asm_stubs.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:150: external/chromium_org/third_party/WebKit/Source/platform/blink_arm_neon.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:151: external/chromium_org/third_party/WebKit/Source/platform/blink_common.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:152: external/chromium_org/third_party/WebKit/Source/platform/blink_platform.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:153: external/chromium_org/third_party/WebKit/Source/platform/blink_prerequisites.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:154: external/chromium_org/third_party/WebKit/Source/platform/make_platform_derived_sources.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:159: external/chromium_org/third_party/WebKit/public/blink_generate_devtools_grd.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:161: external/chromium_org/third_party/angle/src/preprocessor.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:162: external/chromium_org/third_party/angle/src/translator.target.linux-arm.mk: No such file or directory
external/chromium_org/GypAndroid.linux-arm.mk:228: external/chromium_org/v8/tools/gyp/generate_trig_table.host.linux-arm.mk: No such file or directory
"ebtables is disabled on this build"
find: `src': No such file or directory
build/core/base_rules.mk:134: *** prebuilts/misc/common/ub-uiautomator: MODULE.TARGET.JAVA_LIBRARIES.ub-uiautomator already defined by frameworks/uiautomator. Stop.
/home/fadhil/android/zz/out/target/product/nypon/pac_nypon-ota-eng.fadhil.zip doesn't exist!
Click to expand...
Click to collapse
I have no idea what happened.
MuffinIsCute said:
I tried compiling with the XperiaSTE trees and got this error
I have no idea what happened.
Click to expand...
Click to collapse
there are changes in uiautomator in 4.4.3 . repo sync again maybe u have a broken sync
Sent from my Nexus 7
MuffinIsCute said:
I tried compiling with the XperiaSTE trees and got this error
I have no idea what happened.
Click to expand...
Click to collapse
We(PAC team) are currently merging 4.4.3 changes so please don't build until repos are stable.
Cheers,
AJ
MuffinIsCute said:
I tried compiling with the XperiaSTE trees and got this error
I have no idea what happened.
Click to expand...
Click to collapse
from base source directory
cd prebuilts/misc
git revert -m1 490e397ee8b37485ac19967974758dee1db28673
or
rm frameworks/uiautomator
the issue is CM is using a prebuilt version and PAC still has the AOSP from source method in place. I'm using git revert because I prefer the from source method over a prebuilt method. Haven't tested either, but both are technically correct....
skeevydude said:
from base source directory
cd prebuilts/misc
git revert -m1 490e397ee8b37485ac19967974758dee1db28673
or
rm frameworks/uiautomator
the issue is CM is using a prebuilt version and PAC still has the AOSP from source method in place. I'm using git revert because I prefer the from source method over a prebuilt method. Haven't tested either, but both are technically correct....
Click to expand...
Click to collapse
Same error appeared after I used rm -rf frameworks/uiautomator.Resyncing repo.
MuffinIsCute said:
Same error appeared after I used rm -rf frameworks/uiautomator.Resyncing repo.
Click to expand...
Click to collapse
Even after you do that, a crap ton of things need to be merged. Check the gerrit, but all the 4.4.3 merges need to be picked in as well as the main repo manifest being majorly updated. Just got a build error 192 mins in with frameworks/base, that's with all the 4.4.3 picks, Archidroid, gcc 4.8, and the main manifest updates. I normally suck with Java, but I actually figured the error out on my own -- illegal statement start -- CM had the same fix my non-programming self came up with...removing a ")". Time to clean and start a new build.
I'm also doing my builds with Archidroid's Optimizations. Once I get it successfully building, I'm gonna submit that to gerrit along with builder selectable GCC (4.6 to 4.10 with some linaros too) versions (I'm currently hiding his Optimizations in the -o3 option, but I'll make his o4 because I can
If you resync the repo after doing the rm -rf command, it'll add that right back in and you'll still get that error...oh, and rm -rf is the fix in PAC's gerrit right now...sync, do modifications, compile,,,,not mod, sync, compile (I made that mistake plenty of times when I first started out kanging)
skeevydude said:
Even after you do that, a crap ton of things need to be merged. Check the gerrit, but all the 4.4.3 merges need to be picked in as well as the main repo manifest being majorly updated. Just got a build error 192 mins in with frameworks/base, that's with all the 4.4.3 picks, Archidroid, gcc 4.8, and the main manifest updates. I normally suck with Java, but I actually figured the error out on my own -- illegal statement start -- CM had the same fix my non-programming self came up with...removing a ")". Time to clean and start a new build.
I'm also doing my builds with Archidroid's Optimizations. Once I get it successfully building, I'm gonna submit that to gerrit along with builder selectable GCC (4.6 to 4.10 with some linaros too) versions (I'm currently hiding his Optimizations in the -o3 option, but I'll make his o4 because I can
If you resync the repo after doing the rm -rf command, it'll add that right back in and you'll still get that error...oh, and rm -rf is the fix in PAC's gerrit right now...sync, do modifications, compile,,,,not mod, sync, compile (I made that mistake plenty of times when I first started out kanging)
Click to expand...
Click to collapse
Wow... that scared me. If I wait a month, do I still have to do this?
MuffinIsCute said:
Wow... that scared me. If I wait a month, do I still have to do this?
Click to expand...
Click to collapse
Maybe for the next week or two, it usually doesn't take that long in-between minor Android version updates...
All the 4.4.3 gerrit picks can be done inside a half an hour, so it's not like it's that hard.
Try a build now.
AJ
Abhinav2 said:
Try a build now.
AJ
Click to expand...
Click to collapse
While I wait for the repo to sync, let me ask a question, regarding ROMs in general. Besides PA, which ROMs allow you to launch an app in floating mode from the recents list? Does PAC have it yet?
Related
A follow up on this - http://forum.xda-developers.com/showpost.php?p=28177937&postcount=1768 - in the CM9 FXP thread, have I promised to make a little guide.
Guide how I build CM9 for my Mango.
For the first time you try to build CM9.
Create ~/bin and download repo to that directory. Afterwards set executable bit to make it possible to ”execute”.
Code:
mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Now reboot the computer.
Create ~/android/system amd initialize the repository.
Code:
mkdir -p ~/android/system
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
Setup the environmental settings and initialize the Mango build.
Code:
. build/envsetup.sh
brunch mango
Setup the environmental settings and initialize the Mango build.
Code:
git clone git://github.com/TheMuppets/proprietary_vendor_semc.git -b ics ~/android/system/vendor/semc
cd ~/android/system/device/semc/mango/
./setup-makefiles.sh
Download the prebuilts
Code:
~/android/system/vendor/cm/get-prebuilts
Check for new changes
Code:
cd ~/android/system/
repo sync
Setup the environment again and build the ROM (takes long time)
Code:
. build/envsetup.sh
brunch mango
You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-9-DATE-UNOFFICIAL-mango.zip
The next times you try to build it, you only need to do the following.
Delete build.prop, if not will build.prop not get generated.
Code:
rm -f ~/android/system/out/target/product/mango/system/build.prop
Syncronise the git repositories.
Code:
cd ~/android/system/
repo sync
Setup the environmental settings.
Code:
. build/envsetup.sh
Configure/build.
Code:
brunch mango
You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-9-DATE-UNOFFICIAL-mango.zip
If you are trying to build it on a 32bit system, you should change line 374 in ~/android/system/device/semc/msm7x30-common/releasetools/common.py
from:
Code:
cmd = ["java", "-Xmx2048m", "-jar",
to:
Code:
cmd = ["java", "-Xmx1024m", "-jar",
If you get into any trouble, please let me know, I may have missed something.
EDIT (July 2. 2012): I have made a patch to msm7x30-common, so you do not need to edit the file (with this patch does it automatically check if you run on a 64bit or a 32bit system):
http://code.google.com/p/freexperia/issues/detail?id=527
EDIT (July 6. 2012): If there has been an update on git://github.com/koush/proprietary_vendor_semc.git (like there has been today), shall you do the following (pull the updates):
Code:
cd ~/android/system/vendor/semc
git pull
EDIT (July 8. 2012): Adding the following, just before "</manifest>" in ".repo/local_manifest.xml" and the proprietary files will also get updated, when you make a normal "repo sync". Got this idea after talking to Andreas (so thank you Andreas).
Code:
<project name="TheMuppets/proprietary_vendor_semc" path="vendor/semc" remote="github" revision="ics" />
EDIT (July 11. 2012): Changed the proprietary repository from git://github.com/koush/proprietary_vendor_semc.git to git://github.com/TheMuppets/proprietary_vendor_semc.git
allright, i have already synched the cm9 repo. about 5.8 gbs
can you tell me what folders does it include?
edit:took me a few days to download, just don't want to download again
gandhar said:
allright, i have already synched the cm9 repo. about 5.8 gbs
can you tell me what folders does it include?
Click to expand...
Click to collapse
Are you thinking of the "clean" repo?
My ~/android/system/ consists of the following (remember the hidden directories):
abi
android
bionic
bootable
build
dalvik
development
device
external
frameworks
hardware
kernel
libcore
ndk
out
packages
prebuilt
sdk
system
vendor
.repo
.repoconfig
Makefile
You should be able to move your current directory and "just" sync it, to get it up to date.
hnl_dk said:
Are you thinking of the "clean" repo?
My ~/android/system/ consists of the following (remember the hidden directories):
abi
android
bionic
bootable
build
dalvik
development
device
external
frameworks
hardware
kernel
libcore
ndk
out
packages
prebuilt
sdk
system
vendor
.repo
.repoconfig
Makefile
Click to expand...
Click to collapse
allright, out of these except for kernel, out and .repoconfig i have all the others synced.
will using
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
work?
i am missing kernel, out and .repoconfig
gandhar said:
allright, out of these except for kernel, out and .repoconfig i have all the others synced.
will using
Code:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
work?
i am missing kernel, out and .repoconfig
Click to expand...
Click to collapse
They are possibly first created when running brunch the first time. So it should be fine.
successfully building, but getting loads of warnings..
is that normal for the first build?
will report if it boots after compile is over.
gandhar said:
successfully building, but getting loads of warnings..
is that normal for the first build?
will report if it boots after compile is over.
Click to expand...
Click to collapse
There are lots of warnings.
Personally I usually remove all that warnings (using the -Werror option, so warnings get treated as errors) in the projects I am working on. But I understand why it can be a big problem with CM9, that is based on many different projects.
Looking forward to hear if you get a successful built.
hnl_dk said:
There are lots of warnings.
Personally I usually remove all that warnings (using the -Werror option, so warnings get treated as errors) in the projects I am working on. But I understand why it can be a big problem with CM9, that is based on many different projects.
Looking forward to hear if you get a successful built.
Click to expand...
Click to collapse
building will take some time...
well, most warnings are 'some variable has been set but not used', is that much significant?
gandhar said:
building will take some time...
well, most warnings are 'some variable has been set but not used', is that much significant?
Click to expand...
Click to collapse
Yes, first build takes a lot of time... the next times it will be a lot faster.
No that is not very significant, but things like that should still get fixed, to to make it easier to find the significant things.
The less warnings the more easy it is to spot what is important. This also goes for things that should get changed when upgrading to a new major version of the toolchain.
succesfull build!
phone:coconut-wt19i
time: 56 mins for the complete build.
cpu: 2.9 ghz - 4 cores
os:ubuntu 12.04 64 bit
backed up the phone.
boots into recovery
errorless install.
gandhar said:
phone:coconut-wt19i
time: 56 mins for the complete build.
cpu: 2.9 ghz - 4 cores
os:ubuntu 12.04 64 bit
backed up the phone.
boots into recovery
errorless install.
Click to expand...
Click to collapse
Super, looking forward to hear if everything is going to run as as should
hnl_dk said:
Super, looking forward to hear if everything is going to run as as should
Click to expand...
Click to collapse
running fine.
but i see some dependencies missing from the libs needed from
http://wiki.cyanogenmod.com/wiki/Template:Build_from_source_(CM9)
downloading them, will build again later..
is that the reason for the warnings?
gandhar said:
running fine.
but i see some dependencies missing from the libs needed from
http://wiki.cyanogenmod.com/wiki/Template:Build_from_source_(CM9)
downloading them, will build again later..
is that the reason for the warnings?
Click to expand...
Click to collapse
looks like a nice guide that is working with most devices, will save that link
No, the warnings are simply that you rarely find "clean" code, where most warnings have been fixed.
You also need to think of all the code from external projects.
You also only get many of the warnings, if you do not compile the code for some specific platforms.
hnl_dk said:
looks like a nice guide that is working with most devices, will save that link
No, the warnings are simply that you rarely find "clean" code, where most warnings have been fixed.
You also need to think of all the code from external projects.
You also only get many of the warnings, if you do not compile the code for some specific platforms.
Click to expand...
Click to collapse
saw that guide after i started checking for dependencies.
1.hey i see two zips in the output,
one cm-9-20120702-UNOFFICIAL-coconut and other cm_coconut-ota-eng.gandhar
the second is bigger.
i used the first one. why is the second one built i wonder?
2.i think of compiling aosp from source too, but the out folder is 11.3 gbs, what about that?
i do not want to end up falling short on space.
3.this is a system related question, how much will it hinder performance if i move the source to a different internal hd from the main one and build from there?
gandhar said:
saw that guide after i started checking for dependencies.
1.hey i see two zips in the output,
one cm-9-20120702-UNOFFICIAL-coconut and other cm_coconut-ota-eng.gandhar
the second is bigger.
i used the first one. why is the second one built i wonder?
Click to expand...
Click to collapse
Try to read the name ;-)
OTA - Over The Air... I guess that it can mbe used tfor OTA updates, like the mobile companies makes.
gandhar said:
2.i think of compiling aosp from source too, but the out folder is 11.3 gbs, what about that?
i do not want to end up falling short on space.
Click to expand...
Click to collapse
You could do a "make clear", but if you have enough space, would I keep it, so you do not need to wait for the already up to date files.
gandhar said:
3.this is a system related question, how much will it hinder performance if i move the source to a different internal hd from the main one and build from there?
Click to expand...
Click to collapse
There will be no problem with performance, as long as you move it to a HDD that is not too slow.
EDIT (July 2. 2012): I have made a patch to msm7x30-common, so you do not need to edit the file (with this patch does it automatically check if you run on a 64bit or a 32bit system):
http://code.google.com/p/freexperia/issues/detail?id=527
i do a repo sync again, at end of it i get errors on changed files. i think its not replacing the old files.
it's red text
error: bootable/recovery/: CyanogenMod/android_bootable_recovery checkout f8fc12e741d566af215407f35cfc52e5c1cc0023
error: build/: CyanogenMod/android_build checkout df7d6893a59e62c15dd20e306d8280b16969097c
error: external/openssl/: CyanogenMod/android_external_openssl checkout d4004ae717232b83ea445f74c881d9ddc24f589d
error: frameworks/base/: CyanogenMod/android_frameworks_base checkout e0a8c35c1572f0f0dbbda4d871d0a919a79cbe3f
error: hardware/samsung/: CyanogenMod/android_hardware_samsung checkout 23280fc439163a1971956167217283c4ae70bce3
error: packages/apps/Camera/: CyanogenMod/android_packages_apps_Camera checkout 644384a979ec9bd6b237e9031d5afbf592d3056b
error: packages/apps/Settings/: CyanogenMod/android_packages_apps_Settings checkout a946d9a905d460fa9d6c153e031285b566f8d223
error: system/core/: CyanogenMod/android_system_core checkout 389a2fa1d7e4bb8b6be411f272de2e8c92817964
gandhar said:
i do a repo sync again, at end of it i get errors on changed files. i think its not replacing the old files.
it's red text
error: bootable/recovery/: CyanogenMod/android_bootable_recovery checkout f8fc12e741d566af215407f35cfc52e5c1cc0023
error: build/: CyanogenMod/android_build checkout df7d6893a59e62c15dd20e306d8280b16969097c
error: external/openssl/: CyanogenMod/android_external_openssl checkout d4004ae717232b83ea445f74c881d9ddc24f589d
error: frameworks/base/: CyanogenMod/android_frameworks_base checkout e0a8c35c1572f0f0dbbda4d871d0a919a79cbe3f
error: hardware/samsung/: CyanogenMod/android_hardware_samsung checkout 23280fc439163a1971956167217283c4ae70bce3
error: packages/apps/Camera/: CyanogenMod/android_packages_apps_Camera checkout 644384a979ec9bd6b237e9031d5afbf592d3056b
error: packages/apps/Settings/: CyanogenMod/android_packages_apps_Settings checkout a946d9a905d460fa9d6c153e031285b566f8d223
error: system/core/: CyanogenMod/android_system_core checkout 389a2fa1d7e4bb8b6be411f272de2e8c92817964
Click to expand...
Click to collapse
Have not tried that.
You can try to do a "repo forall -c git reset --hard" this "resets" all the repositories (removes all changes, also if something has been corrupted).
hnl_dk said:
Have not tried that.
You can try to do a "repo forall -c git reset --hard" this "resets" all the repositories.
Click to expand...
Click to collapse
will it redownload?
Hey everyone,
I'm trying to build Jellybean from source for the HTC Desire. I've synced the repository and cloned a CyanogenMod fork for the Desire and I've also pulled my proprietary files from my device. I did the source/envsetup.sh and then ran lunch and selected my device but then it runs in to the error that says "device/htc/common/common.mk" Does not exist. Can anyone help me? Much appreciated.
Sent from my HTC One X using Tapatalk 2
Okay I managed to get past my problem by clone a git of the android_device_htc_common files. But when I go to make I run in to the issue of this
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.1
TARGET_PRODUCT=full_bravo
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.0.0-22-generic-i686-athlon-with-Ubuntu-11.10-oneiric
HOST_BUILD_TYPE=release
BUILD_ID=JRO03C
OUT_DIR=out
============================================
Checking build tools versions...
build/core/base_rules.mk:171: *** device/htc/bravo/libsensors: MODULE.TARGET.SHARED_LIBRARIES.sensors.bravo already defined by device/bravo/libsensors. Stop.
[email protected]:~/WORKING_DIRECTORY$
Any help is greatly appreciated. I'm almost there I think! Thanks.
If someone could help me with my latest issue or turn me in the direction of an IRC or something where someone will actually try to help that would be awesome. Thanks a lot.
Lastest Issue:
Code:
Directory: out/target/product/bravo/root/sbin
Directory: out/target/product/bravo/root/dev
Directory: out/target/product/bravo/root/proc
Directory: out/target/product/bravo/root/sys
Directory: out/target/product/bravo/root/system
Directory: out/target/product/bravo/root/data
Export includes file: bionic/libc/Android.mk -- out/target/product/bravo/obj/SHARED_LIBRARIES/libc_intermediates/export_includes
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc -mthumb-interwork -Ibionic/libc/private -DCRT_LEGACY_WORKAROUND -Ibionic/libc/private -Ibionic/libc/arch-arm/include -o out/target/product/bravo/obj/lib/crtbegin_static.o -c bionic/libc/arch-arm/bionic/crtbegin_static.S
Export includes file: bionic/libstdc++/Android.mk -- out/target/product/bravo/obj/SHARED_LIBRARIES/libstdc++_intermediates/export_includes
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file
make: *** [out/target/product/bravo/obj/lib/crtbegin_static.o] Error 126
make: *** Waiting for unfinished jobs....
Sorry, can't help with this but..side question
How do you pull proprietary files from device?
Aquethys said:
Sorry, can't help with this but..side question
How do you pull proprietary files from device?
Click to expand...
Click to collapse
When you pull your device files off of github or wherever you got them, there is a script called extract-files.sh and you have to have your device connected with USB debugging enabled and have ADB setup on your computer and then you run the script and it will pull them for you.
Sent from my HTC One X using Tapatalk 2
BUMP
Sent from my HTC One X using Tapatalk 2
Draciel882 said:
If someone could help me with my latest issue or turn me in the direction of an IRC or something where someone will actually try to help that would be awesome. Thanks a lot.
Lastest Issue:
Code:
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file
Click to expand...
Click to collapse
This. Install an x86_64 os to your host or look at cm9 source to figure out how to rebuild the toolchain for x86. You can try
Code:
file prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc
on my just-synced jb src, it shows
Code:
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0xf8e11f40cf6b10fa26e6fea774d9d94058c53595, stripped
which basically means I'm also sucking with my i686 debian
you can probably edit the manifest.xml in .repo or android (one of them should work, editing the other will break repo, so be careful) and replace paths to toolchain with cm9 ones
sp3dev said:
This. Install an x86_64 os to your host or look at cm9 source to figure out how to rebuild the toolchain for x86. You can try
Code:
file prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc
on my just-synced jb src, it shows
Code:
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, BuildID[sha1]=0xf8e11f40cf6b10fa26e6fea774d9d94058c53595, stripped
which basically means I'm also sucking with my i686 debian
you can probably edit the manifest.xml in .repo or android (one of them should work, editing the other will break repo, so be careful) and replace paths to toolchain with cm9 ones
Click to expand...
Click to collapse
Thanks a lot. I got a machine running on 64 Ubuntu 11.10 and all those errors are fixed. Now I'm having this issue though:
Code:
Which would you like? [full-eng] 8
build/core/product_config.mk:205: *** No matches for product "full_bravo". Stop.
** Don't have a product spec for: 'full_bravo'
** Do you have the right repo manifest?
On the tutorial I'm using, there are some VERY vague instructions on how to fix this. If someone could give me a detailed procedure on how to fix this I would be extremely happy. Thanks.
Bump
Sent from my HTC One X using Tapatalk 2
If anyone could help me, I would be extremely grateful. This is the last problem I have I believe before it will actually build.
Bump
Sent from my HTC One X using Tapatalk 2
I've been racking my brain about this for a while now (whenever I've had some spare time over the past week or so) and scouring the internets in search of an answer but either I'm not very good at searching, or there aren't very many people doing what I'm doing that do not already know the answer to my question.
Here's what I would like to do. I have completed a full build of AOKP for my device (GSII Skyrocket). If I were to make an edit to a system app package, Contacts in particular, how can I rebuild the package without redoing an entire build? I am aware of the "mmm" command, but if I run
Code:
$ mmm packages/apps/Contacts
$ make packages/apps/Contacts
$ make Contacts
or any derivation of that command, it defaults to building:
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76I
which then immediately craps out because it's building for a generic product which has no kernel source configured:
Code:
make: Entering directory `/home/m4570d0n/AOKP'
build/core/tasks/kernel.mk:53: **********************************************************
build/core/tasks/kernel.mk:54: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:55: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:56: * AndroidBoard.mk file *
build/core/tasks/kernel.mk:57: **********************************************************
build/core/tasks/kernel.mk:58: *** "NO KERNEL CONFIG". Stop
make: Leaving directory `/home/m4570d0n/AOKP'
When I was building CM9 it would actually make a Contacts.apk in /out/target/product/generic, but even then it was mdpi, odexed, and pretty much garbage.
What I'm trying to figure out (and rather surprised that I haven't found more info on it yet), is what configuration changes do I have to make or flags that I have to set so that I can just rebuild Contacts in the same way it would get built if I were doing a full build for the skyrocket so that I can incorporate the changes I made to the Contacts package? (Obviously this question would apply for any device, I'm just using the Skyrocket as an example since that's the device for which I'm building.)
On a similar note, if I can get that first question resolved, can I just add:
Code:
LOCAL_AAPT_FLAGS := -c xhdpi -x 10
to my Android.mk for Contacts if I wanted to build contacts with xhdpi resources? Would that work?
this is probably the most useful info I've come across (in addition to the stuff on developer.android.com) but it seems like some of it is now outdated and I'm not sure if it addresses my particular question.
http://www.jokersax.com/dev-guides/android-building-faqs/
http://elinux.org/Android_aapt
Any help would be much appreciated.
Just type.
make Contacts
Sent from my Galaxy Nexus using xda premium
As I mentioned in my post, I have tried that.
m4570d0n said:
As I mentioned in my post, I have tried that.
Click to expand...
Click to collapse
Well that's how you build just one app.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
Well that's how you build just one app.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I am aware. That was not my question though. That command by itself will build one app by looking to build/target/product/full.mk which has:
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/board/generic/device.mk)
PRODUCT_NAME := full
PRODUCT_DEVICE := generic
PRODUCT_BRAND := Android
PRODUCT_MODEL := Full Android on Emulator
That's not going to work. What I'm trying to do is build it so that it looks to my device configuration which would be this:
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
$(call inherit-product, device/samsung/skyrocket/device.mk)
PRODUCT_NAME := full_skyrocket
PRODUCT_DEVICE := skyrocket
PRODUCT_BRAND := samsung
PRODUCT_MANUFACTURER := samsung
PRODUCT_MODEL := SAMSUNG-SGH-I727
Then use lunch and select your device. Maybe I'm just not understanding why you are doing so strange.
Sent from my Galaxy Nexus using xda premium
I'm not trying to do an entire build though. That's exactly what I'm trying to avoid. I just want to rebuild one package based on my device configuration and current built sources in /out. I am not trying to make an app for a generic device/board to run on an emulator, which is what the "make Contacts" command will try to do by default.
m4570d0n said:
I'm not trying to do an entire build though. That's exactly what I'm trying to avoid. I just want to rebuild one package based on my device configuration and current built sources in /out. I am not trying to make an app for a generic device/board to run on an emulator, which is what the "make Contacts" command will try to do by default.
Click to expand...
Click to collapse
I do what you are all the time. For example. I make clean and clobber. Use lunch to load my device and build a specific app. I like my Mms with the holo dark theme and built just that. IRS possible you will come into errors while building though if that app needs other files compiled. If you are trying to make an app more "universal" do a port and build it in eclipse against the framework you need to.
Sent from my Galaxy Nexus using xda premium
oh wow. I'm retarded. I usually use brunch or use lunch aokp_skyrocket-userdebug && mka bacon 2> warn.log
or something like that. For some reason I was thinking that after I used lunch and selected my device it would automatically start doing an entire build. That worked though. Thank you!
Now, I had that LOCAL_AAPT_FLAG in the Android.mk for Contacts, but it still built the apk with hdpi resources. How might I be able to flag it to use xhdpi instead? The reason I ask is that I know that this build will work on the Galaxy Note even with the hdpi images, but would like to build a version with xhdpi instead.
I am not sure I understand clearly, but how exactly did you manage to go past
Code:
build/core/tasks/kernel.mk:68: **********************************************************
build/core/tasks/kernel.mk:69: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:70: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:71: * BoardConfig.mk file *
build/core/tasks/kernel.mk:72: **********************************************************
toxicthunder said:
I am not sure I understand clearly, but how exactly did you manage to go past
Code:
build/core/tasks/kernel.mk:68: **********************************************************
build/core/tasks/kernel.mk:69: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:70: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:71: * BoardConfig.mk file *
build/core/tasks/kernel.mk:72: **********************************************************
Click to expand...
Click to collapse
Let's say I want to build Contacts.apk from CM10 for the Skyrocket. The commands would be:
Code:
. /build/envsetup.sh
lunch cm_skyrocket-userdebug
make Contacts
It will build Contacts.apk and put it in the /out/target/produce/skyrocket/system/app/ directory.
My confusion when I created this thread was that I thought the lunch [device] command would start the build like the brunch command does, but all it does is essentially load the build configuration for the device. The "mka bacon" command is what will start a full build. The lunch command is the same as the breakfast command, except you can select devices that are not officially supported. The brunch command is the equivalent of "breakfast [device] && mka bacon".
That said, I'm not sure if the squisher and opticharger scripts are run when you build just one package this way, but my guess is that they are not.
glad its all working out
This is still unofficial. This thread is intended for devs & advanced users only.
Guide how I build CM10.1 for my smultron.
For the first time you try to build CM10.1
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Download & install lzop compression tool
Code:
sudo apt-get install lzop
Initialize the CyanogenMod source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.1/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Get the prebuilts
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
Setup the environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-10.1-DATE-UNOFFICIAL-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.1/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Setup the environment
Code:
. build/envsetup.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-10.1-DATE-UNOFFICIAL-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Credits: Thanks to hnl_dk for the initial CM9 & CM10 guides.
Build is successful using this guide now. You can build for all xperia 2011 phones by replacing "smultron" with your device's name in the guide.
More info can be found here: https://github.com/LegacyXperia/local_manifests/wiki
Re: [GUIDE][WIP] How I build my own CM10.1 test builds
Wew good guide! :thumbup: hope can get the stable version of the CM10.1with this guide here
Sent from my SK17i using xda premium
After 'repo init' there should be a
Code:
mkdir -p ~/android/system/.repo/local_manifests
Script to apply not yet merged changes:
Code:
#!/bin/sh
android=~/android/system
#http://review.cyanogenmod.org/#/c/32906/
cd ${android}/frameworks/av/
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_av refs/changes/06/32906/2 && git format-patch -1 --stdout FETCH_HEAD | patch -p1
#http://review.cyanogenmod.org/#/c/28336/
cd ${android}/packages/apps/LegacyCamera/
git fetch http://review.cyanogenmod.org/CyanogenMod/android_packages_apps_LegacyCamera refs/changes/36/28336/1 && git format-patch -1 --stdout FETCH_HEAD | patch -p1
#http://review.cyanogenmod.org/#/c/34989/
cd ${android}/hardware/qcom/audio-caf
git fetch http://review.cyanogenmod.org/CyanogenMod/android_hardware_qcom_audio-caf refs/changes/89/34989/5 && git format-patch -1 --stdout FETCH_HEAD | patch -p1
From http://forum.xda-developers.com/showthread.php?t=1358547
Code:
repo sync -f
May fix error: Exited sync due to fetch errors
hi,
I want to build CM 10.1 for my mango, guide is perfectly explain, just one question :
does i need to add the script part explain by M66B two post above or it's outdated and i just need to follow the first post ?
Thanks
Edit : sorry for the noob question, i have read the reviews and have my answer
kosmo666 said:
hi,
I want to build CM 10.1 for my mango, guide is perfectly explain, just one question :
does i need to add the script part explain by M66B two post above or it's outdated and i just need to follow the first post ?
Thanks
Edit : sorry for the noob question, i have read the reviews and have my answer
Click to expand...
Click to collapse
The scrip parts from above are outdated, we maintain this script now.
How to merge in this nAa 3.4.45 kernel sources? Is it connected with kernel sources?
mastero9017 said:
How to merge in this nAa 3.4.45 kernel sources? Is it connected with kernel sources?
Click to expand...
Click to collapse
If you look at Mike's github (https://github.com/LegacyXperia)
you'll see that he maintains his own branch of the nAa kernel (https://github.com/LegacyXperia/msm7x30-3.4.x-nAa).
They are not the same, but similar (Mike currently has more changes, since nAa hasn't updated anything for two weeks).
-> If you build Mike's sources, you'll also get a 3.4.45 kernel.
What am I doing wrong? Did everything, checked all libs 10 times..
EDIT: It's a KDE error,aghhr. Delete/clean /root/.config directory fixes it
Code:
[email protected]:~/android/system# brunch haida
including vendor/cm/vendorsetup.sh
Trying dependencies-only mode on a non-existing device tree?
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
CM_VERSION=10.1-20130603-UNOFFICIAL-haida
TARGET_PRODUCT=cm_haida
TARGET_BUILD_VARIANT=userdebug
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-41-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39E
OUT_DIR=/root/android/system/out
============================================
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
CM_VERSION=10.1-20130603-UNOFFICIAL-haida
TARGET_PRODUCT=cm_haida
TARGET_BUILD_VARIANT=userdebug
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-41-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39E
OUT_DIR=/root/android/system/out
============================================
make: *** /.config: is a directory. Stop.
Guys,
For your info Windows Host NTFS file system is case insensitive and will break android compilation!!!
Workaround: Create a new virtual hdd with ext3 format and mount it to your ubuntu guest! Sad that ntfs cannot be used.
So, below is for your info if u came across this post. It is useful for sharing folders between Linux guest and Windows host.
IF you are using Virtualbox on a Win7/8 host system,
To use Shared Folder feature and add automount (note, VirtualBox needs to be run as Administrator so that os.symlink works!!!!
In Windows:
1. Go to your VirtualMachine Folder and look for MyVM.vbox,
2. Open with notepad++
3. Look for <ExtraData>
4. Add this inside the <ExtraData></ExtraData>
Code:
<ExtraDataItem name="VBoxInternal2/SharedFoldersEnableSymlinksCreate/android" value="1"/>
where "android" is my shared folder!!! =)
In terminal:
Code:
sudo nano /etc/fstab
Add this line:
Code:
/android /home/myName/android vboxsf rw,uid=1000,gid=1000 0 0
where android is the folder I give when sharing in SharedFolder of the VirtualBox and /home/myName/android is the folder I created in Ubuntu.
Ctrl+O and hit Enter to save. Ctrl+X to quit. and Reboot and you are done.
Also, if you encounter error or Virtualbox/ubuntu hung on repo sync, add -j2 or -j3 to prevent race condition!!!
Code:
repo sync -j3
Syncing work tree error!!!
If you encounter syn error
Code:
Fetching projects: 100% (204/224), done.
Syncing work tree: 90% (204/224) error: manifest required for this command -- please run init
1. Go to "android\system\.repo\"
2. Open "project.list" with notepad or notepad++
3. Go to the line of error. In this case, line 204 as above.
4. E.g. Ling 204 shows: external/wpa_supplicant_6, So, go to the folder "android\system\external\wpa_supplicant_6" and delete ".git" folder
5. Go back to Terminal and "repo sync"
=)
You need the lz4 compression tool from now on to be able to build the kernel. First post is updated with instructions on how to get it.
Code:
sudo apt-get install subversion
cd ~/Downloads
svn checkout -r 91 http://lz4.googlecode.com/svn/trunk/ lz4
cd lz4 && make && cp lz4demo ~/bin/lz4demo
Can any body please tell me,what's the exact size of full cm10.1. Source repo
I had set my laptop to download repo from last 32 hours
And till now more than 8gb data was downloaded ....
And how to know how much data left for download...?
Can anybody give me the exact size of the gits which are to be download so that I can compare that sizes with the files which I had downloaded....?
Sent from my Xperia Mini Pro
Hey @mikeioannina,
Do you have any guide on repo branch? In windows, git gui is easy to do. But I'm not familiar with ubuntu.
How do you branch out the project without error?
I tried in ~/android/system:
Code:
repo start kernel-patch .
it says . project not found. What the hell. Needa branch and test some codes!!! =)
Also, is there a private directory for us to put binary to system/apps or scripts which will not be affected by "repo sync" during compilation?
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
hijagdeep said:
Can any body please tell me,what's the exact size of full cm10.1. Source repo
I had set my laptop to download repo from last 32 hours
And till now more than 8gb data was downloaded ....
And how to know how much data left for download...?
Can anybody give me the exact size of the gits which are to be download so that I can compare that sizes with the files which I had downloaded....?
Sent from my Xperia Mini Pro
Click to expand...
Click to collapse
It's around ~25GB. Maybe less due to compression. ^_^
shenlong85 said:
It's around ~25GB. Maybe less due to compression. ^_^
Click to expand...
Click to collapse
Someone told me that its around 8 gb
Sent from my Xperia Mini Pro
hijagdeep said:
Someone told me that its around 8 gb
Sent from my Xperia Mini Pro
Click to expand...
Click to collapse
If you initiated with the CM10.1 branch, it will be 14Gig, if you initiated with no branch, 25Gig
Langes said:
If you initiated with the CM10.1 branch, it will be 14Gig, if you initiated with no branch, 25Gig
Click to expand...
Click to collapse
I have initiated with this repo command
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and also used this local manifests
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.github.com/LegacyXperia/local_manifests/master/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
and now 25 hours are passed and it downloaded 9.5gb data ..
hijagdeep said:
I have initiated with this repo command
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and also used this local manifests
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.github.com/LegacyXperia/local_manifests/master/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
and now 25 hours are passed and it downloaded 9.5gb data ..
Click to expand...
Click to collapse
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1 is for the whole cm10.1 sources. Be patient. Are you using full blown linux host or just a virtual machine? IF you are using virtual machine, it may be slow and have race condition during repo which results in errors. Try using
Code:
repo sync -j3
For 3 simultaneous thread or j2 depending on the number of core in your processor and whether there is hyperthreading. It'll make it more stable.
Hello everyone.
I would like to build clean AOSP 4.3 for haida/hallon for personal use. Also I am planning to share builds here if someone wants to try.
But I need your help to figure out how to put all needed stuff to make a working build. The only problem what confuses me is Sony libs.
I have A8 laptop and 4 Mbps connection and Arch Linux is my main operating system, so I am experienced with building Linux apps from source. I used Slackware and Gentoo before, so I learned a lot about compiling kernel and source.
Also I have tried to port Nexus S AOSP, but only far I got is stuck on Nexus logo (bootloop), resolution is similar, but not the same.
I have read mike's thread about building CM 10.1 from source, but I am confused about where all stuff goes (which folder to put what?). So, I am figuring it out: http://forum.xda-developers.com/showthread.php?t=2164696
Is this ok to repo init AOSP instead of CM and then follow the rest guide (local manifests and etc)?
I mean, just replace this line
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
with this: repo init -u https://android.googlesource.com/platform/manifest
Thanks in advance.
Ok, I'm getting it
I included kernel, mogami-common, msm7x30, haida and vendor from LegacyXperia and it seems to be in right folders. Now I'm missing recovery.
I'm nearly done with build so please help. I get this error:
make -j5 otapackage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3
TARGET_PRODUCT=full_haida
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-1-ARCH-x86_64-with-glibc2.2.5
HOST_BUILD_TYPE=release
BUILD_ID=JSS15Q
OUT_DIR=out
============================================
Checking build tools versions...
hardware/ti/wlan/mac80211/wpa_supplicant_lib/Android.mk:15: /android.config: Datei oder Verzeichnis nicht gefunden
No private recovery resources for TARGET_DEVICE haida
No recovery.fstab for TARGET_DEVICE haida
make: *** Keine Regel, um »/android.config« zu erstellen. Schluss.
What I need to do now?
Maybe @pcfighter wil help you as he is quiet experienced in building AOSP for our devices. You can pm him maybe
Sent from my MT11i using Tapatalk 2