FORUMS
Remove All Ads from XDA
Honor 7x
Win an Honor 7X!

Compiling ICS from source. help needed!

1,429 posts
Thanks Meter: 1,569
 
By djpbx, Inactive Recognized Developer on 7th May 2012, 12:51 PM
Post Reply Email Thread
Hi there!

I'm trying to compile ics from source (AOSP), but i'm having some problems, hope some people can help me out.

I'm on Ubuntu 10.04, i have sun-java6-jdk and all the neccesairy packages installed. And of course, I want to compile for our nice Desire S.

i'm running into two issues.
1. i've been searching GitHub for device files, but i only found CM9 ones (which i can't use because they are for compiling cm9), and ics saga proprietary files, thanks to koush.
2. when i try and build for any device (for example here maguro), i get the message:
Code:
make: *** No rule to make target '/lib/tools.jar', needed by 'out/target/common/docs/doc-comment-check-timestamp'. Stop.
Can you guys help me out?


FIXING THE ISSUES
Issue 1
- pulled files from m-deejay his git.

Issue 2
I fixed the 2nd problem by throwing the command:
Code:
export ANDROID_JAVA_HOME=$JAVA_HOME
Issue 3
See 3rd post in this thread.
 
 
7th May 2012, 01:56 PM |#2  
dan-fish's Avatar
Senior Member
Thanks Meter: 423
 
More
The device tree from nexx's github is your best bet. The only other one there is for the desire s can be found on m-deejay's github but it's quite old. You can get the proprietary files by running the extract-files.sh found in the device folder while your phone is connected with adb.

Sent from my Desire S using Tapatalk 2
The Following User Says Thank You to dan-fish For This Useful Post: [ View ] Gift dan-fish Ad-Free
8th May 2012, 12:56 PM |#3  
djpbx's Avatar
OP Inactive Recognized Developer
Flag Breda, the Netherlands
Thanks Meter: 1,569
 
Donate to Me
More
k. i got the saga files from m-deejays source and i got the proprietary files. now i got this issue...
Code:
build/core/base_rules.mk:78: *** Module name: lights.msm7x30
build/core/base_rules.mk:79: *** Makefile location: hardware/msm7k/liblights
build/core/base_rules.mk:80: * 
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: * 
build/core/base_rules.mk:84: *     optional, debug, eng, tests, samples
build/core/base_rules.mk:85: * 
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag: 
build/core/base_rules.mk:89: * 
build/core/base_rules.mk:90: *    Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: *    Android.mk for the affected module, and add
build/core/base_rules.mk:92: *    the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: *    into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: *    makefile(s) where it's necessary, if
build/core/base_rules.mk:95: *    appropriate.
build/core/base_rules.mk:96: * 
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: * 
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules.  Stop.
any idea?
8th May 2012, 03:07 PM |#4  
Tectas's Avatar
Senior Member
Thanks Meter: 2,977
 
More
Quote:
Originally Posted by djpbx

k. i got the saga files from m-deejays source and i got the proprietary files. now i got this issue...

Code:
build/core/base_rules.mk:78: *** Module name: lights.msm7x30
build/core/base_rules.mk:79: *** Makefile location: hardware/msm7k/liblights
build/core/base_rules.mk:80: * 
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: * 
build/core/base_rules.mk:84: *     optional, debug, eng, tests, samples
build/core/base_rules.mk:85: * 
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag: 
build/core/base_rules.mk:89: * 
build/core/base_rules.mk:90: *    Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: *    Android.mk for the affected module, and add
build/core/base_rules.mk:92: *    the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: *    into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: *    makefile(s) where it's necessary, if
build/core/base_rules.mk:95: *    appropriate.
build/core/base_rules.mk:96: * 
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: * 
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules.  Stop.
any idea?

Yes, switch to the repo from nexx, m-deejay made the last commit 4 months ago.
If you don't want to, add
Code:
LOCAL_MODULE_TAGS := optional
at hardware/msm7k/liblights/Android.mk and also
Code:
 lights.msm7x30
at device/htc/saga/saga.mk at the PRODUCT_PACKAGES key.
The Following 2 Users Say Thank You to Tectas For This Useful Post: [ View ] Gift Tectas Ad-Free
8th May 2012, 04:11 PM |#5  
djpbx's Avatar
OP Inactive Recognized Developer
Flag Breda, the Netherlands
Thanks Meter: 1,569
 
Donate to Me
More
Quote:
Originally Posted by Tectas

Yes, switch to the repo from nexx, m-deejay made the last commit 4 months ago.
If you don't want to, add

Code:
LOCAL_MODULE_TAGS := optional
at hardware/msm7k/liblights/Android.mk and also
Code:
 lights.msm7x30
at device/htc/saga/saga.mk at the PRODUCT_PACKAGES key.

thanks!

but when i add nexx' repo files, lunch gives me only the option for cm saga build. is that ok too?
8th May 2012, 07:21 PM |#6  
Tectas's Avatar
Senior Member
Thanks Meter: 2,977
 
More
Quote:
Originally Posted by djpbx

thanks!

but when i add nexx' repo files, lunch gives me only the option for cm saga build. is that ok too?

Should not matter, but you can change it inside device/HTC/saga/cm.mk at PRODUCT_NAME.

Gesendet von meinem HTC Desire S mit Tapatalk 2
The Following User Says Thank You to Tectas For This Useful Post: [ View ] Gift Tectas Ad-Free
9th May 2012, 07:15 PM |#7  
djpbx's Avatar
OP Inactive Recognized Developer
Flag Breda, the Netherlands
Thanks Meter: 1,569
 
Donate to Me
More
Quote:
Originally Posted by Tectas

Should not matter, but you can change it inside device/HTC/saga/cm.mk at PRODUCT_NAME.

Gesendet von meinem HTC Desire S mit Tapatalk 2

- k, downloaded nexx' source, corrected the name (for lunch) to full_saga-userdebug instead of cm_saga-userdebug in vendorsetup.sh
- lunched
- got the same lights issue, got it fixed
- got a similar error about gralloc.msm7x30. added the optional local module tags too, at the top of the file (underneath the license blabla), added gralloc.msm7x30 to device.mk at the right place, but still got the error. any idea?
9th May 2012, 07:21 PM |#8  
amidabuddha's Avatar
Senior Member
Thanks Meter: 2,459
 
More
Sorry if not relevant but have you tried with brunch instead? I saw here that lunch is good for building for Android emulator and unsupported devices. But since Nexx is working on it mka bacon may be functional... Just an assumptions since I have no dev experience
9th May 2012, 08:36 PM |#9  
djpbx's Avatar
OP Inactive Recognized Developer
Flag Breda, the Netherlands
Thanks Meter: 1,569
 
Donate to Me
More
Quote:
Originally Posted by amidabuddha

Sorry if not relevant but have you tried with brunch instead? I saw here that lunch is good for building for Android emulator and unsupported devices. But since Nexx is working on it mka bacon may be functional... Just an assumptions since I have no dev experience

Going to give it a shot asap
10th May 2012, 06:05 PM |#10  
djpbx's Avatar
OP Inactive Recognized Developer
Flag Breda, the Netherlands
Thanks Meter: 1,569
 
Donate to Me
More
Lol. did not even recognise lunch, breakfast, brunch or mka.

aren't they CM specific build commands? I try to build AOSP...


-------------------

nevermind. got past all the issues (placed the local module tags everywhere 'make' asked me to.
but, this error is weird. anyone know the fix?

Code:
make: *** No rule to make target `hardware/qcom/gps/loc_api/libloc_api-rpc/inc-50000/loc_api_cb.h', needed by `out/target/product/saga/obj/include/libloc_api-rpc/inc/loc_api_cb.h'.  Stop.
make: *** Waiting for unfinished jobs....
Header: out/target/product/saga/obj/include/librpc/rpc/xdr.h
danny@targatus:~/WORKING_ANDROIDSOURCE$
----------------

k, found out i' m missing the hardware/qcom/gps/loc_api/libloc_api-rpc/inc-50000/ folder, any idea how i should get it?

Repo syncing anyways.
18th May 2012, 10:23 AM |#11  
djpbx's Avatar
OP Inactive Recognized Developer
Flag Breda, the Netherlands
Thanks Meter: 1,569
 
Donate to Me
More
Hi there, an update

So i switched to the CM9 source, and got it to build very easily. make otapackage and flashed it to my device. used nexx' kernel / modules just to be sure.

now i got this error:
Code:
I/ServiceManager( 1203): service 'media.audio_flinger' died
I/ServiceManager( 1203): service 'media.player' died
I/ServiceManager( 1203): service 'media.camera' died
I/ServiceManager( 1203): service 'media.audio_policy' died
at the end of my logcat, which causes a bootloop.

any idea?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes