• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[GUIDE][DEV]Compiling CM9/10/10.1 for ZTE Skate

115 posts in this topic

Posted

Thanks. Have fixed it all I think. git pull should fix the errors.

0

Share this post


Link to post
Share on other sites

Posted

This is what I'm getting now..


*** No rule to make target `vendor/cm/proprietary/RomManager.apk', needed by `out/target/product/skate/system/app/RomManager.apk'. Stop.


0

Share this post


Link to post
Share on other sites

Posted

Try running get-prebuilts again.

0

Share this post


Link to post
Share on other sites

Posted

dear gurus

how does one bring private tree up to date ?

Here is what I tried:

cm9 $ repo sync -j4

Fetching projects: 100% (254/254), done.

Syncing work tree: 6% (16/254) fatal: reference is not a tree: 8d25781706ecd0ae50f2b130e8dd08c57296de5c

Syncing work tree: 100% (254/254), done.

device/zte/skate/: leaving ics; does not track upstream

error: device/zte/skate/: CyanogenMod/android_device_zte_skate checkout 8d25781706ecd0ae50f2b130e8dd08c57296de5c

and (not sure if git-pull is correct way, sorry, not yet familiar with git...):

cm9 $ cd ~/cm9/device/zte

zte $ git pull git://github.com/ColdFusionX/android_device_zte_skate.git skate

fatal: Not a git repository (or any of the parent directories): .git

any help to provide correct commands appreciated

thanks

0

Share this post


Link to post
Share on other sites

Posted

Not sure about the first problem, but for the second

cd ~/cm9/device/zte/skate

git pull git://github.com/ColdFusionX/android_device_zte_skate.git 

0

Share this post


Link to post
Share on other sites

Posted

thanks !!!

this works also for git://github.com/koush/proprietary_vendor_zte.git

cm9$ cd ~/cm9/device/zte/skate

skate$ git pull git://github.com/ColdFusionX/android_device_zte_skate.git

From git://github.com/ColdFusionX/android_device_zte_skate

* branch HEAD -> FETCH_HEAD

Already up-to-date.

...

cm9$ cd ~/cm9/vendor/zte/proprietary_vendor_zte

proprietary_vendor_zte $ git pull git://github.com/koush/proprietary_vendor_zte.git

From git://github.com/koush/proprietary_vendor_zte

* branch HEAD -> FETCH_HEAD

Already up-to-date.

...

but for zte-kernel-msm7x27 I see

cm9$ cd ~/cm9/kernel/zte/zte-kernel-msm7x27

zte-kernel-msm7x27$ git pull git://github.com/CyanogenMod/zte-kernel-msm7x27.git

From git://github.com/CyanogenMod/zte-kernel-msm7x27

* branch HEAD -> FETCH_HEAD

Auto-merging drivers/power/ti_gauge.c

Auto-merging drivers/power/msm_battery.c

Auto-merging drivers/power/Kconfig

Auto-merging drivers/input/touchscreen/synaptics_i2c_rmi.c

CONFLICT (content): Merge conflict in drivers/input/touchscreen/synaptics_i2c_rmi.c

Auto-merging drivers/input/touchscreen/synaptics_3k.c

CONFLICT (content): Merge conflict in drivers/input/touchscreen/synaptics_3k.c

Auto-merging arch/arm/mach-msm/board-zte-v9.c

Auto-merging arch/arm/mach-msm/board-zte-blade2.c

CONFLICT (add/add): Merge conflict in arch/arm/mach-msm/board-zte-blade2.c

Auto-merging arch/arm/mach-msm/board-zte-blade2-keypad.c

CONFLICT (add/add): Merge conflict in arch/arm/mach-msm/board-zte-blade2-keypad.c

Auto-merging arch/arm/mach-msm/board-zte-blade.c

CONFLICT (content): Merge conflict in arch/arm/mach-msm/board-zte-blade.c

Auto-merging arch/arm/mach-msm/Kconfig

Auto-merging arch/arm/configs/cyanogen_v9_defconfig

CONFLICT (content): Merge conflict in arch/arm/configs/cyanogen_v9_defconfig

Automatic merge failed; fix conflicts and then commit the result.

trying again:

zte-kernel-msm7x27$ git pull git://github.com/CyanogenMod/zte-kernel-msm7x27.git

U arch/arm/configs/cyanogen_v9_defconfig

M arch/arm/configs/cyanogen_v9_recovery_defconfig

A arch/arm/configs/msm7627_blade2_p736v_defconfig

M arch/arm/mach-msm/Kconfig

U arch/arm/mach-msm/board-zte-blade.c

U arch/arm/mach-msm/board-zte-blade2-keypad.c

U arch/arm/mach-msm/board-zte-blade2.c

M arch/arm/mach-msm/board-zte-v9.c

M arch/arm/mm/Kconfig

U drivers/input/touchscreen/synaptics_3k.c

U drivers/input/touchscreen/synaptics_i2c_rmi.c

M drivers/power/Kconfig

M drivers/power/msm_battery.c

M drivers/power/ti_gauge.c

Pull is not possible because you have unmerged files.

Please, fix them up in the work tree, and then use 'git add/rm <file>'

as appropriate to mark resolution, or use 'git commit -a'.

of course I can remove zte-kernel-msm7x27 and clone, but then rebuild

is from scratch on that subtree

0

Share this post


Link to post
Share on other sites

Posted

Hi skate compiling people

I couple of questions before I dare to attempt to flash own built

.zip.

First, why do I want to build myself?

- Just for fun

- I would like to use USB storage (via kernel config)

(as to be able to, say, play music from an USB stick)

- I would perhaps like to use a DVB-T stick (via kernel config)

(to use once vlc for android is ready)

- I would perhaps want to have a slightly different set of apps

(but I don't know yet how to do that)

- ...

So here the questions

- if I flash minor upgrade, do I need to wipe anything?

- build system_size says (int) 230686720 and my /system partition df = 220M

also: 220*1024*1024 = 230686720

does this mean that my /system partition will be 100% full?

- unlike

update-cm-9-20120531-SNAPSHOT-skate-ColdFusionX-tilal6991-signed.zip,

my zip also has an extra directory with videoeditor app and media

files.

I don't need them, but will they be flashed, and, where?

Can I just unzip, throw them away and make a zip file without?

- todays zip is called cm-9-20120608-UNOFFICIAL-skate.zip whereas

yesterday's zip was called

update-cm-9-20120607-SNAPSHOT-skate-signed.zip

Is this name change intentional?

Thanks for all help

have a good weekend

0

Share this post


Link to post
Share on other sites

Posted

Hi skate compiling people

I couple of questions before I dare to attempt to flash own built

.zip.

First, why do I want to build myself?

- Just for fun

- I would like to use USB storage (via kernel config)

(as to be able to, say, play music from an USB stick)

- I would perhaps like to use a DVB-T stick (via kernel config)

(to use once vlc for android is ready)

- I would perhaps want to have a slightly different set of apps

(but I don't know yet how to do that)

- ...

So here the questions

- if I flash minor upgrade, do I need to wipe anything?

- build system_size says (int) 230686720 and my /system partition df = 220M

also: 220*1024*1024 = 230686720

does this mean that my /system partition will be 100% full?

- unlike

update-cm-9-20120531-SNAPSHOT-skate-ColdFusionX-tilal6991-signed.zip,

my zip also has an extra directory with videoeditor app and media

files.

I don't need them, but will they be flashed, and, where?

Can I just unzip, throw them away and make a zip file without?

- todays zip is called cm-9-20120608-UNOFFICIAL-skate.zip whereas

yesterday's zip was called

update-cm-9-20120607-SNAPSHOT-skate-signed.zip

Is this name change intentional?

Thanks for all help

have a good weekend

-No wipes

-Not sure

-Look in Meta-Inf/com/android/google to see where they are flashed, you will most likely just be able to delete them form the zip

-Did you

export CM_SNAPSHOT=1

????

1

Share this post


Link to post
Share on other sites

Posted

thanks razzmataz for pointing me at meta inf scripts

~cm9$ echo $CM_SNAPSHOT

1

0

Share this post


Link to post
Share on other sites

Posted

Sorry to ask ... I am not a git connoisseur

How does one pull a snapshot, say, date 20120615, from cm9 and zte

repository?

Also: are certain snapshots (perhaps weeklies) more 'stable' than

others?

Say, I like and trust tilal6991's snapshot (which, in fact, I do, of

course) and I want to change a tiny bit (but I do not want to end up

in some, perhaps, unstable situation).

Thanks!

0

Share this post


Link to post
Share on other sites

Posted

recently (2 days) build fails:

device/zte/skate/overlay/frameworks/base/core/res/res/values/dimens.xml:4: error: Error parsing XML: junk after document element

make: *** [out/target/common/obj/APPS/framework-res_intermediates/package-export.apk] Error 1

make: *** Deleting file `out/target/common/obj/APPS/framework-res_intermediates/package-export.apk'

but the xml looks not bad to me:

cat device/zte/skate/overlay/frameworks/base/core/res/res/values/dimens.xml

<!-- Height of the horizontal navigation bar on devices that require it -->

<dimen name="navigation_bar_height">36dp</dimen>

<!-- Width of the vertical navigation bar on devices that require it -->

<dimen name="navigation_bar_width">42dp</dimen>

anybody sees this?

0

Share this post


Link to post
Share on other sites

Posted

git pull the skate repo.

1

Share this post


Link to post
Share on other sites

Posted (edited)

Thanks for the kind help.

Pardon my lack of git command knowledge, I do undestand how some

version control systems work but not git.

It seems somehow I have an unmerged file that cannot be automatically

resolved. (arch/arm/configs/cyanogen_v9_defconfig).

Of course, right now, I am not planning to commit anything, just play

around a bit.

Any hint on how to resolve (and, perhaps, avoid) the conflict?

PS: some time ago I have, for test purpose, done a make config and,

perhaps, I copied the .config to cyanogen_v9_defconfig, but then,

meanwhile I have removed the local entire zte-kernel-msm7x27 directory

several times.

# cd ~/cm9/kernel/zte/zte-kernel-msm7x27

# git pull git://github.com/CyanogenMod/zte-kernel-msm7x27.git

From git://github.com/CyanogenMod/zte-kernel-msm7x27

* branch HEAD -> FETCH_HEAD

Auto-merging drivers/power/ti_gauge.c

Auto-merging drivers/power/msm_battery.c

Auto-merging drivers/power/Kconfig

Auto-merging drivers/input/touchscreen/synaptics_i2c_rmi.c

CONFLICT (content): Merge conflict in drivers/input/touchscreen/synaptics_i2c_rmi.c

Auto-merging drivers/input/touchscreen/synaptics_3k.c

CONFLICT (content): Merge conflict in drivers/input/touchscreen/synaptics_3k.c

Auto-merging arch/arm/mach-msm/board-zte-v9.c

Auto-merging arch/arm/mach-msm/board-zte-blade2.c

CONFLICT (add/add): Merge conflict in arch/arm/mach-msm/board-zte-blade2.c

Auto-merging arch/arm/mach-msm/board-zte-blade2-keypad.c

CONFLICT (add/add): Merge conflict in arch/arm/mach-msm/board-zte-blade2-keypad.c

Auto-merging arch/arm/mach-msm/board-zte-blade.c

CONFLICT (content): Merge conflict in arch/arm/mach-msm/board-zte-blade.c

Auto-merging arch/arm/mach-msm/Kconfig

Auto-merging arch/arm/configs/cyanogen_v9_defconfig

CONFLICT (content): Merge conflict in arch/arm/configs/cyanogen_v9_defconfig

Automatic merge failed; fix conflicts and then commit the result.

# git pull git://github.com/CyanogenMod/zte-kernel-msm7x27.git

U arch/arm/configs/cyanogen_v9_defconfig

M arch/arm/configs/cyanogen_v9_recovery_defconfig

A arch/arm/configs/msm7627_blade2_p736v_defconfig

M arch/arm/mach-msm/Kconfig

U arch/arm/mach-msm/board-zte-blade.c

U arch/arm/mach-msm/board-zte-blade2-keypad.c

U arch/arm/mach-msm/board-zte-blade2.c

M arch/arm/mach-msm/board-zte-v9.c

M arch/arm/mm/Kconfig

U drivers/input/touchscreen/synaptics_3k.c

U drivers/input/touchscreen/synaptics_i2c_rmi.c

M drivers/power/Kconfig

M drivers/power/msm_battery.c

M drivers/power/ti_gauge.c

Pull is not possible because you have unmerged files.

Please, fix them up in the work tree, and then use 'git add/rm <file>'

as appropriate to mark resolution, or use 'git commit -a'.

Edited by Nofan Tasi
0

Share this post


Link to post
Share on other sites

Posted

I'm no expert either but shouldn't all of the blade bits be Skate

0

Share this post


Link to post
Share on other sites

Posted

The kernel git includes the blade crescent (blade 2) skate and v9 so no they're fine.

0

Share this post


Link to post
Share on other sites

Posted

thanks everybody

perhaps I changed a file and this must be cached somewhere because even after removal of tree and cloning it back, merging cannot be resolved.

I tried a few things like

git init ...

git reset ...

but I do not know well what I am doing (I do read the manpages) and it does not alter the conflict

have a nice day

0

Share this post


Link to post
Share on other sites

Posted

restart from scratch made build recipe work again

now that code freeze cm9 branch is made, do we need to adapt recipe ?

thanks!

0

Share this post


Link to post
Share on other sites

Posted

Downloading CM10 source, anything that needs to be changed for it to compile? Patches etc..

0

Share this post


Link to post
Share on other sites

Posted

I am tempted to wait for CM9 release and get its build instructions then ;-)

0

Share this post


Link to post
Share on other sites

Posted (edited)

I'm going to try to compile including the patches Konsta has on his guide. I'll let you know if it works.

Now I'm stuck, what kernel do I use? The same one as ICS, or Konsta's kernel?

Edited by razzmataz1478
0

Share this post


Link to post
Share on other sites

Posted

I'm getting this error in the kernel when trying to compile:


Note: Some input files use or override a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

drivers/usb/gadget/Kconfig:849:warning: defaults for choice values not supported

drivers/usb/gadget/Kconfig:1053:warning: defaults for choice values not supported


0

Share this post


Link to post
Share on other sites

Posted

Those are warnings not errors

The errors will be further up.

0

Share this post


Link to post
Share on other sites

Posted

OK I'll compile again and the errors...

0

Share this post


Link to post
Share on other sites

Posted

It won't even start compiling now..

external/v8/Android.mk:22: WARNING: Building on ARM with non-ARMv7 variant. On ARM, V8 is well tested only on ARMv7.

find: ‘src’: No such file or directory

PRODUCT_COPY_FILES vendor/zte/skate/proprietary/etc/init.qcom.bt.sh:system/etc/init.qcom.bt.sh ignored.

build/core/Makefile:38: warning: overriding commands for target `out/target/product/skate/system/bin/hciattach'

build/core/base_rules.mk:529: warning: ignoring old commands for target `out/target/product/skate/system/bin/hciattach'

PRODUCT_COPY_FILES frameworks/native/data/etc/android.software.sip.voip.xml:system/etc/permissions/android.software.sip.voip.xml ignored.

build/core/Makefile:38: warning: overriding commands for target `out/target/product/skate/system/etc/mkshrc'

build/core/base_rules.mk:529: warning: ignoring old commands for target `out/target/product/skate/system/etc/mkshrc'

No private recovery resources for TARGET_DEVICE skate

host Executable: mkbootimg (out/host/linux-x86/obj/EXECUTABLES/mkbootimg_intermediates/mkbootimg)

host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)

make -C kernel/zte/zte-kernel-msm7x27 O=/home/razzmataz1478/skate/cm10/out/target/product/skate/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/razzmataz1478/skate/cm10/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-" cyanogen_skate_defconfig

make[1]: Entering directory `/home/razzmataz1478/skate/cm10/kernel/zte/zte-kernel-msm7x27'

target thumb C: libc_common <= bionic/libc/bionic/semaphore.c

true

target thumb C: libc_common <= bionic/libc/bionic/tdelete.c

true

target thumb C: libc_common <= bionic/libc/bionic/tdestroy.c

In file included from bionic/libc/private/bionic_atomic_inline.h:53:0,

				 from bionic/libc/bionic/semaphore.c:33:

bionic/libc/private/bionic_atomic_arm.h:54:4: warning: #warning Rebuilding this source file in ARM mode is highly recommended for performance!! [-Wcpp]

In file included from bionic/libc/private/bionic_atomic_inline.h:53:0,

				 from bionic/libc/bionic/semaphore.c:33:

bionic/libc/private/bionic_atomic_arm.h: In function '__sem_dec':

bionic/libc/private/bionic_atomic_arm.h:144:9: error: unknown register name 'r3cc' in 'asm'

bionic/libc/private/bionic_atomic_arm.h: In function '__sem_trydec':

bionic/libc/private/bionic_atomic_arm.h:144:9: error: unknown register name 'r3cc' in 'asm'

bionic/libc/private/bionic_atomic_arm.h: In function 'sem_post':

bionic/libc/private/bionic_atomic_arm.h:144:9: error: unknown register name 'r3cc' in 'asm'

make: *** [out/target/product/skate/obj/STATIC_LIBRARIES/libc_common_intermediates/bionic/semaphore.o] Error 1

make: *** Waiting for unfinished jobs....

  GEN	 /home/razzmataz1478/skate/cm10/out/target/product/skate/obj/KERNEL_OBJ/Makefile

drivers/usb/gadget/Kconfig:849:warning: defaults for choice values not supported

drivers/usb/gadget/Kconfig:1053:warning: defaults for choice values not supported

#

# configuration written to .config

#


0

Share this post


Link to post
Share on other sites

Posted (edited)

Done make clean and it seems to be building now...

Here's the error:


In file included from bionic/libc/private/bionic_atomic_inline.h:53:0,

				 from bionic/libstdc++/src/one_time_construction.cpp:15:

bionic/libc/private/bionic_atomic_arm.h:54:4: warning: #warning Rebuilding this source file in ARM mode is highly recommended for performance!! [-Wcpp]

target thumb C++: libstdc++ <= bionic/libstdc++/src/new.cpp

bionic/libc/private/bionic_atomic_arm.h: In function 'int __cxa_guard_acquire(_guard_t*)':

bionic/libc/private/bionic_atomic_arm.h:156:38: error: unknown register name 'r3cc' in 'asm'

bionic/libc/private/bionic_atomic_arm.h:156:38: error: unknown register name 'r3cc' in 'asm'

bionic/libc/private/bionic_atomic_arm.h: In function 'void __cxa_guard_release(_guard_t*)':

bionic/libc/private/bionic_atomic_arm.h:156:38: error: unknown register name 'r3cc' in 'asm'

make: *** [out/target/product/skate/obj/SHARED_LIBRARIES/libstdc++_intermediates/src/one_time_construction.o] Error 1

make: *** Waiting for unfinished jobs....

  GEN	 /home/razzmataz1478/skate/cm10/out/target/product/skate/obj/KERNEL_OBJ/Makefile

  HOSTCC  scripts/basic/hash

  HOSTCC  scripts/kconfig/conf.o

  HOSTCC  scripts/kconfig/kxgettext.o

  SHIPPED scripts/kconfig/zconf.tab.c

  SHIPPED scripts/kconfig/lex.zconf.c

  SHIPPED scripts/kconfig/zconf.hash.c

  HOSTCC  scripts/kconfig/zconf.tab.o

  HOSTLD  scripts/kconfig/conf

Note: Some input files use or override a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

drivers/usb/gadget/Kconfig:849:warning: defaults for choice values not supported

drivers/usb/gadget/Kconfig:1053:warning: defaults for choice values not supported

#

# configuration written to .config


This is a few minutes into the build on my Ubuntu 12 VM allocated with 3 3GHz cores and 5GB ram

Edited by razzmataz1478
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.