[Q] Having trouble building CM7 from source using OS X - Android Software/Hacking General [Developers Only]

So I've been trying to build CM7 from source following this guide. I follow it exactly (apart from replacing "Vision" with "Glacier" and "-froyo" with "-gingerbread") and it gives me an error when I enter in the command "make -j`sysctl -an hw.logicalcpu` bacon"
"make: *** No rule to make target `vendor/htc/glacier/proprietary/MS-HTCVISION-KNT20-02.apk', needed by `out/target/product/glacier/system/app/MS-HTCVISION-KNT20-02.apk'. Stop.
make: *** Waiting for unfinished jobs...."
And countless other ones during the process.
Any idea why this is happening? I'm on OS X if it helps.

I think I've waiting long enough to warrant a bump.
Anyone?

ELBdelorean said:
So I've been trying to build CM7 from source following this guide. I follow it exactly (apart from replacing "Vision" with "Glacier" and "-froyo" with "-gingerbread") and it gives me an error when I enter in the command "make -j`sysctl -an hw.logicalcpu` bacon"
"make: *** No rule to make target `vendor/htc/glacier/proprietary/MS-HTCVISION-KNT20-02.apk', needed by `out/target/product/glacier/system/app/MS-HTCVISION-KNT20-02.apk'. Stop.
make: *** Waiting for unfinished jobs...."
And countless other ones during the process.
Any idea why this is happening? I'm on OS X if it helps.
Click to expand...
Click to collapse
My first thought for what's wrong is that you have the latest version of gmake(3.82) which has a bug that prevents android from building. If you haven't already done so, downgrade to gmake 3.81 and see if that solves your problem. You can do that following the step-by-step from the AOSP build guide or the instructions in this post.

Yes, I have downgraded gmake.

Ok, I think I figured out why you're getting the error which sounds like it gets thrown when the proprietary files are not pulled from your phone through adb when you run extract-files.sh as they should. From here:
make: *** No rule to make target `.../[something]', needed by `.../[something]'. Stop.
You need to copy the proprietary files off your phone. Make sure you have ADB set up and plug your device to your computer via USB. Then run:
Code:
cd /Volumes/CyanogenModWorkspace/android/system/device/htc/glacier/
./extract-files.sh
Click to expand...
Click to collapse
Hopefully that will get you up and running.

Related

compiling cupcake for the htc dream

Are people able to compile the current cupcake code for the target dream?
I can't seem to get it to work at all.
I can successfully make the generic target -- then I followed the directions on the google site;
http://source.android.com/documentation/building-for-dream
Compilation appears to be working fine - though it stops at the following;
Code:
In file included from frameworks/base/libs/audioflinger/AudioResamplerCubic.cpp:20:
system/core/include/cutils/log.h:68:1: warning: this is the location of the previous definition
target thumb C++: libaudioflinger <= frameworks/base/libs/audioflinger/AudioFlinger.cpp
make: *** No rule to make target `out/target/product/dream/obj/lib/libaudio.so', needed by `out/target/product/dream/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/LINKED/libaudioflinger.so'. Stop.
Has anyone seen this?
strazzere said:
Are people able to compile the current cupcake code for the target dream?
I can't seem to get it to work at all.
I can successfully make the generic target -- then I followed the directions on the google site;
http://source.android.com/documentation/building-for-dream
Compilation appears to be working fine - though it stops at the following;
Code:
In file included from frameworks/base/libs/audioflinger/AudioResamplerCubic.cpp:20:
system/core/include/cutils/log.h:68:1: warning: this is the location of the previous definition
target thumb C++: libaudioflinger <= frameworks/base/libs/audioflinger/AudioFlinger.cpp
make: *** No rule to make target `out/target/product/dream/obj/lib/libaudio.so', needed by `out/target/product/dream/obj/SHARED_LIBRARIES/libaudioflinger_intermediates/LINKED/libaudioflinger.so'. Stop.
Has anyone seen this?
Click to expand...
Click to collapse
Doh! Silly me -- maybe this is what the vague comment on the sticky ment by they should have added "it" to the extract.sh
This file off the device was needed, go it by running the following;
Code:
adb pull /system/lib/libaudio.so proprietary/libaudio.so
ugh - so dumb tonight.. sorry mods
Is the newest build any better? Last I heard, it was slow and buggy.

Trying to compile CM 12.1 with no luck so far because of Terminal errors.

So I used @kylevessPL's "ready" configuration ( https://github.com/kylevessPL/android_device_lge_l70pn ) for our device's CM 12.1 to try to compile it and see what happens.
But with no luck, unfortunately. For some reason, when I execute the brunch command, errors show up.
Here's an example of one of the a lot similar errors that appear just right after the previous one was fixed: http://pastebin.com/KkhjttJB .
The exact error here is:
"Notice file: external/zip/NOTICE -- /home/max-pc/cm-12.1/out/target/product/l70pn/obj/NOTICE_FILES/src//system/xbin/zip.txt
make: *** No rule to make target `device/lge/l70pn/prebuilt/usr/keylayout/Generic-290.kl', needed by `/home/max-pc/cm-12.1/out/target/product/l70pn/system/usr/keylayout/Generic-D290.kl'. Stop."
P.S: You can also see the Terminal error in the picture attached to the post.
P.S. 2: I did NOT execute the "vendor/cm/get-prebuilts" command in "Initializing repo" section, because it always says: "bash: vendor/cm/get-prebuilts: No such file or directory"
proudlytm said:
So I used @kylevessPL's "ready" configuration ( https://github.com/kylevessPL/android_device_lge_l70pn ) for our device's CM 12.1 to try to compile it and see what happens.
But with no luck, unfortunately. For some reason, when I execute the brunch command, errors show up.
Here's an example of one of the a lot similar errors that appear just right after the previous one was fixed: http://pastebin.com/KkhjttJB .
The exact error here is:
"Notice file: external/zip/NOTICE -- /home/max-pc/cm-12.1/out/target/product/l70pn/obj/NOTICE_FILES/src//system/xbin/zip.txt
make: *** No rule to make target `device/lge/l70pn/prebuilt/usr/keylayout/Generic-290.kl', needed by `/home/max-pc/cm-12.1/out/target/product/l70pn/system/usr/keylayout/Generic-D290.kl'. Stop."
P.S: You can also see the Terminal error in the picture attached to the post.
P.S. 2: I did NOT execute the "vendor/cm/get-prebuilts" command in "Initializing repo" section, because it always says: "bash: vendor/cm/get-prebuilts: No such file or directory"
Click to expand...
Click to collapse
Renames "l70pn" to the original "l70pds".... or edit the following lines;
in the path "device/lge/l70pds/device_l70pds.mk
the_naxhoo said:
Renames "l70pn" to the original "l70pds".... or edit the following lines;
in the path "device/lge/l70pds/device_l70pds.mk
Click to expand...
Click to collapse
I just tried but I don't know the new compile command. Can you tell it to me ? When I do it with cm_l70pds-userdebug instead with cm_l70pn-userdebug command, this happens:
[email protected]:~/cm-12.1$ brunch cm_l70pds-userdebug
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
Device l70pds not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for l70pds not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_l70pds'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
proudlytm said:
I just tried but I don't know the new compile command. Can you tell it to me ? When I do it with cm_l70pds-userdebug instead with cm_l70pn-userdebug command, this happens:
[email protected]:~/cm-12.1$ brunch cm_l70pds-userdebug
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
Device l70pds not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for l70pds not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/lge/l70pds/cm.mk]]: "device/lge/l70pn/full_l70pn.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_l70pds'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Click to expand...
Click to collapse
no no no, my mistake, i'm sorry... you should use Github "VM03". Or my Github ( https://github.com/ignacio28 )
just change "device/lge/l70pds/prebuilt/usr/keylayout/Generic-290.kl:system/usr/keylayout/Generic-D290.kl" to "device/lge/l70pds/prebuilt/usr/keylayout/Generic-D290.kl:system/usr/keylayout/Generic-D290.kl" in the file "device_170pn.mk"
@proudlytm Would you like to do a telegram group for compilation on LG L Fino? @the_naxhoo is helping me with the compilation. If both of you tells me what to do i can help. I have already CM 12.1 sources downloads so maybe i can do something with my computer
carliquiss said:
@proudlytm Would you like to do a telegram group for compilation on LG L Fino? @the_naxhoo is helping me with the compilation. If both of you tells me what to do i can help. I have already CM 12.1 sources downloads so maybe i can do something with my computer
Click to expand...
Click to collapse
I wish I could help but I accidentally hard bricked my phone and I'm gonna take it to the place I bought it from and they're either gonna get it exchanged for a new one, or they will repair it. I think it will take like 1 week for everything to be done.
proudlytm said:
I wish I could help but I accidentally hard bricked my phone and I'm gonna take it to the place I bought it from and they're either gonna get it exchanged for a new one, or they will repair it. I think it will take like 1 week for everything to be done.
Click to expand...
Click to collapse
Okey no problem, if you want you can help is debugging the compilation and we can try in our smartphones. If you are interested send me a pm with your telegram name
Enviado desde mi Zippers 5 mediante Tapatalk

[Completed] Ninja_wrapper error

building my very first nougat ROM for the GT-I9505 (Jfltexx) but I keep getting this error when use the brunch command.
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/lochlan/LAOS/out/target/product/jfltexx/obj/lib/libtime_genoff.so.toc', needed by '/home/lochlan/LAOS/out/target/product/jfltexx/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
I've done some research and still haven't come to a conclusion on what the hell it means...
Any and all help would be nice!
skyskidder said:
building my very first nougat ROM for the GT-I9505 (Jfltexx) but I keep getting this error when use the brunch command.
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/lochlan/LAOS/out/target/product/jfltexx/obj/lib/libtime_genoff.so.toc', needed by '/home/lochlan/LAOS/out/target/product/jfltexx/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
I've done some research and still haven't come to a conclusion on what the hell it means...
Any and all help would be nice!
Click to expand...
Click to collapse
Did you get the vendor repo for your device? Please pay attention on this. I think your vendor repo is outdated and file libtime_genoff.so is missing.
blinoff82 said:
Did you get the vendor repo for your device? Please pay attention on this. I think your vendor repo is outdated and file libtime_genoff.so is missing.
Click to expand...
Click to collapse
Hello, this is what I'm using for my vendor repo
https://github.com/JDCTeam/android_vendor_cm
And you are correct about libtime_genoff.so is missing. I checked all my repos for that file and have gotten no results. Any idea on what I should do?
P.S. Thanks for your help thus far! It means a lot!
skyskidder said:
Hello, this is what I'm using for my vendor repo
https://github.com/JDCTeam/android_vendor_cm
And you are correct about libtime_genoff.so is missing. I checked all my repos for that file and have gotten no results. Any idea on what I should do?
P.S. Thanks for your help thus far! It means a lot!
Click to expand...
Click to collapse
You should use another vendor blobs like this https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-7.1/jflte.
Add in local_manifest (roomservice.xml):
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" revision="android-7.1" remote="github" />
Then: "repo sync -j1 --force-sync" and build again.
I never encountered with Samsung devices, I hope I did not make a mistake with path...
blinoff82 said:
You should use another vendor blobs like this https://github.com/DonkeyCoyote/proprietary_vendor_samsung/tree/android-7.1/jflte.
Add in local_manifest (roomservice.xml):
<project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" revision="android-7.1" remote="github" />
Then: "repo sync -j1 --force-sync" and build again.
I never encountered with Samsung devices, I hope I did not make a mistake with path...
Click to expand...
Click to collapse
Hey thanks for the idea on using this new repo for the device blobs and providing the link! But i have a few questions.
#1. There are severely many less files in this new repo. Why is that?
#2 This effect anything with my rom? if so like what?
You dont need to give me a full out explanation a brief one will do if you can, if you cant dont sweat it!
I will also try this new repo when i get home and I'll update you on how it goes.
Thank you so very much!
-Sky
skyskidder said:
#1. There are severely many less files in this new repo. Why is that?
#2 This effect anything with my rom? if so like what?
Click to expand...
Click to collapse
1. Because this repo ONLY for jflte.
2. No effect, this is just blobs needed for your device and for compilation.
blinoff82 said:
1. Because this repo ONLY for jflte.
2. No effect, this is just blobs needed for your device and for compilation.
Click to expand...
Click to collapse
Welp. I tried what you told me to do and Ive gotten farther but i ran into another error.
FAILED: /bin/bash -c "(make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= cyanogenmod_jf_defconfig ) && (if [ ! -z "" ]; then echo "Overriding kernel config with ''"; echo >> /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config; make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" oldconfig; fi ) && (make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" savedefconfig ) && (if [ ! -z "" ]; then echo "Using additional config ''"; kernel/samsung/jf/scripts/kconfig/merge_config.sh -m -O /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config kernel/samsung/jf/arch/arm/configs/; make -j2 -C kernel/samsung/jf O=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE="/home/lochlan/LAOS/prebuilts/misc/linux-x86/ccache/ccache arm-linux-androidkernel-" KCONFIG_ALLCONFIG=/home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/.config alldefconfig; fi )"
make: Entering directory '/home/lochlan/LAOS/kernel/samsung/jf'
GEN /home/lochlan/LAOS/out/target/product/jfltexx/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/basic/fixdep
/home/lochlan/LAOS/kernel/samsung/jf/scripts/basic/fixdep.c:106:23: fatal error: sys/types.h: No such file or directory
compilation terminated.
scripts/Makefile.host:118: recipe for target 'scripts/basic/fixdep' failed
make[2]: *** [scripts/basic/fixdep] Error 1
/home/lochlan/LAOS/kernel/samsung/jf/Makefile:417: recipe for target 'scripts_basic' failed
make[1]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make: *** [sub-make] Error 2
make: Leaving directory '/home/lochlan/LAOS/kernel/samsung/jf'
[ 6% 2204/33925] target R.java/Manifest.java: framework-res (/home/lochlan/LAOS/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp)
warning: string 'candidates_style' has no default translation.
warning: string 'gsm_alphabet_default_charset' has no default translation.
warning: string 'wfcSpnFormat' has no default translation.
nothing matches overlay file default_wallpaper.png, for flavor hdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xhdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xxhdpi-v4
nothing matches overlay file default_wallpaper.png, for flavor xxxhdpi-v4
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/lochlan/LAOS'
#### make failed to build some targets (08:00 (mm:ss)) ####
Click to expand...
Click to collapse
Any idea what this error is?
Sorry my friend you should think for yourself. That's all.
http://stackoverflow.com/questions/37771339/sys-types-h-no-such-file-or-directory
:QUICK UPDATE:
I don't think I'm ready to tackle a project of this scale yet. My frustration, lack of knowledge of compiling and knowledge of repo commands, java, and the damn terminal have caused as of now to post pone my attempts at making a ROM. With exams coming up I have take EVEN MORE time away from my attempts.
:SIDE NOTES:
I feel I have made some progress since the last post I have made with the help of @binoff82 of course. Slowly but surely I'm getting there. With the expense of many broken things in my room... Including a fractured wrist...
In a few days and or weeks time I will update the thread with another post either explaining my progress or if I'm just going to halt my attempts completely for quite a while.
-Sky
P.S. I should probably take anger management classes...
skyskidder said:
:QUICK UPDATE:
I don't think I'm ready to tackle a project of this scale yet. My frustration, lack of knowledge of compiling and knowledge of repo commands, java, and the damn terminal have caused as of now to post pone my attempts at making a ROM. With exams coming up I have take EVEN MORE time away from my attempts.
:SIDE NOTES:
I feel I have made some progress since the last post I have made with the help of @binoff82 of course. Slowly but surely I'm getting there. With the expense of many broken things in my room... Including a fractured wrist...
In a few days and or weeks time I will update the thread with another post either explaining my progress or if I'm just going to halt my attempts completely for quite a while.
-Sky
P.S. I should probably take anger management classes...
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you seen this excellent guide by jackeagle ?
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
that thread is probably your best bet for advice
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. Have you seen this excellent guide by jackeagle ?
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
that thread is probably your best bet for advice
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Hi, thanks for taking your time to help me. Sadly this is the original guide I have been following when attempting to build my ROM.

Resurrection Remix nougat sync error

I'm trying to download Resurrection Remix repo files. Already downloaded 32GB but then at a point it showed me this error and the sync exited :
Fetching projects : 100% (586/586)
error: Exited sync due to fetch errors
I even tried with repo sync -f but it didn't work. Same error at that particular point. Please somebody tell me what to do. I dont want this 32GB to be a waste.
You need to scroll up and see which repo is failing to sync. Then you can try to figure it what the problem with that one is.
jisoo said:
You need to scroll up and see which repo is failing to sync. Then you can try to figure it what the problem with that one is.
Click to expand...
Click to collapse
Oh I see, acrually there are many files which are showing error while fetching ( "error: cannot fetch platform/prebuilts/go/darwin-x86" and many more). But the thing is how do I fix this ? I have a stable network connection but how can i download those particular files which are not being fetched ?
Suvam Mondal said:
Oh I see, acrually there are many files which are showing error while fetching ( "error: cannot fetch platform/prebuilts/go/darwin-x86" and many more). But the thing is how do I fix this ? I have a stable network connection but how can i download those particular files which are not being fetched ?
Click to expand...
Click to collapse
The repository is either not there anymore, or the branch which repo is looking for doesn't exist.
You can have a look at the manifest in .repo/manifest.xml to see in more detail which URL and branch this is.
How did you get this manifest file (i.e. how did you init your repo) which has such non-existing repos?
jisoo said:
The repository is either not there anymore, or the branch which repo is looking for doesn't exist.
You can have a look at the manifest in .repo/manifest.xml to see in more detail which URL and branch this is.
How did you get this manifest file (i.e. how did you init your repo) which has such non-existing repos?
Click to expand...
Click to collapse
Dont know, just followed the instructions in the Resurrection Remix github page.
However, restarted my pc and that error seemed to be fixed, but got this error at the last step of the process(i.e, during uncompression of files)
I have attached the log file. Please have a look and tell me what to do.
Suvam Mondal said:
Dont know, just followed the instructions in the Resurrection Remix github page.
However, restarted my pc and that error seemed to be fixed, but got this error at the last step of the process(i.e, during uncompression of files)
I have attached the log file. Please have a look and tell me what to do.
Click to expand...
Click to collapse
It looks like there was some errors downloading some of the hardware/qcom repositories, and some of the files are corrupt. That really should not happen by itself, and you may have other bigger issues happening with your VM.
Anyway, you have the option of deleting everything and starting from scratch. If you don't want to do that, you can try deleting the ".repo/project-objects/LineageOS/hardware_qcom_media.git/" and possibly the other hardware_qcom folders. This may remove all the corrupted files as well, and let you re-download only those repositories by doing "repo sync" later.
If repo is able to finish successfully, you should at least have non-corrupted files for the build, though as I said you may have some deeper filesystem corruption issues going on as well.
jisoo said:
It looks like there was some errors downloading some of the hardware/qcom repositories, and some of the files are corrupt. That really should not happen by itself, and you may have other bigger issues happening with your VM.
Anyway, you have the option of deleting everything and starting from scratch. If you don't want to do that, you can try deleting the ".repo/project-objects/LineageOS/hardware_qcom_media.git/" and possibly the other hardware_qcom folders. This may remove all the corrupted files as well, and let you re-download only those repositories by doing "repo sync" later.
If repo is able to finish successfully, you should at least have non-corrupted files for the build, though as I said you may have some deeper filesystem corruption issues going on as well.
Click to expand...
Click to collapse
Thank you very much, it worked. Successfully downloaded the repo files :
But now I'm stuck at the breakfast codename step
My device(Meizu m2 note) has no codename, you know any alternate way for this step ?
Suvam Mondal said:
Thank you very much, it worked. Successfully downloaded the repo files :
But now I'm stuck at the breakfast codename step
My device(Meizu m2 note) has no codename, you know any alternate way for this step ?
Click to expand...
Click to collapse
That would be because RR doesn't officially support this device, and therefore the device and kernel trees are not in the repo probably.
You'll need to port the device yourself, which may be difficult or easy (depending on your experience and how well supported the device generally is).
I had a quick look, and it's probably best if you use source trees from the dev who builds for LineageOS: https://github.com/Moyster?tab=repositories
You'll want to be familiar with the basics of git and github for this, I think.
Best way to figure out what is needed to port a device to another ROM is to compare the device trees of an identical device on the 2 different ROMs. So for instance, because I have a Nexus 5X (bullhead), I would compare the device_lge_bullhead repos in both Resurrection Remix and LineageOS, in order to figure out what I need to add to port a LineageOS device tree to Resurrection Remix.
Anyway, that's pretty much all I can suggest. If you have any specific question, feel free to post here or send me a PM.
Good luck!
jisoo said:
That would be because RR doesn't officially support this device, and therefore the device and kernel trees are not in the repo probably.
You'll need to port the device yourself, which may be difficult or easy (depending on your experience and how well supported the device generally is).
I had a quick look, and it's probably best if you use source trees from the dev who builds for LineageOS: https://github.com/Moyster?tab=repositories
You'll want to be familiar with the basics of git and github for this, I think.
Best way to figure out what is needed to port a device to another ROM is to compare the device trees of an identical device on the 2 different ROMs. So for instance, because I have a Nexus 5X (bullhead), I would compare the device_lge_bullhead repos in both Resurrection Remix and LineageOS, in order to figure out what I need to add to port a LineageOS device tree to Resurrection Remix.
Anyway, that's pretty much all I can suggest. If you have any specific question, feel free to post here or send me a PM.
Good luck!
Click to expand...
Click to collapse
Yes, almost there. This is the first time I am building a ROM, very excited
But i got this error while building the ROM. First i tried with USE_NINJA which gave some error build-lineage_m2note.ninja failed to make. Then I tried with USE_NINJA=false which gave me this error(log file).
I have attached the log file. Please tell me what to do. I followed every step still I got this error, that also in the final step . :crying:
Suvam Mondal said:
Yes, almost there. This is the first time I am building a ROM, very excited
But i got this error while building the ROM. First i tried with USE_NINJA which gave some error build-lineage_m2note.ninja failed to make. Then I tried with USE_NINJA=false which gave me this error(log file).
I have attached the log file. Please tell me what to do. I followed every step still I got this error, that also in the final step . :crying:
Click to expand...
Click to collapse
I would stick with not adding any specific definition for the build, and just using the standard variables (so not adding USE_NINJA true or false), and then having a look at the error messages there.
At least, I won't be able to help much otherwise, as I always just use the default settings for the build.
In the log you attached, there's a bunch of "Cannot allocate memory" errors. I would have a look at the kernel logs as well (you can get these with the "dmesg" command, or using "cat /var/log/kern.log"). You will probably see what is causing the error from here, as it seems to be related to the OS itself.
You may have out of memory (OOM) issues, which is common with nougat builds. To fix that, you can follow the instructions here: http://stackoverflow.com/questions/...ror-try-increasing-heap-size-with-java-option
jisoo said:
I would stick with not adding any specific definition for the build, and just using the standard variables (so not adding USE_NINJA true or false), and then having a look at the error messages there.
At least, I won't be able to help much otherwise, as I always just use the default settings for the build.
In the log you attached, there's a bunch of "Cannot allocate memory" errors. I would have a look at the kernel logs as well (you can get these with the "dmesg" command, or using "cat /var/log/kern.log"). You will probably see what is causing the error from here, as it seems to be related to the OS itself.
You may have out of memory (OOM) issues, which is common with nougat builds. To fix that, you can follow the instructions here: http://stackoverflow.com/questions/...ror-try-increasing-heap-size-with-java-option
Click to expand...
Click to collapse
Did that. But now I am facing this nina_wrapper error 1 at 99% of compilation
Code:
[ 99% 3295/3298] Docs droiddoc: /home/...t/target/common/docs/doc-comment-check
FAILED: /bin/bash /home/suvam/rr/out/target/common/docs/doc-comment-check-timestamp.rsp
frameworks/base/core/java/android/provider/Settings.java:3657: error 101: Unresolved link/see tag "android.provider.Settings.Global#KEY_SMS_BREATH" in android.provider.Settings.System
frameworks/base/core/java/android/widget/SeekBar.java:41: error 101: Unresolved link/see tag "ProgressBar#setMax(int)" in android.preference.CustomSeekBarPreference
DroidDoc took 345 sec. to write docs to /home/suvam/rr/out/target/common/docs/doc-comment-check
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Suvam Mondal said:
Did that. But now I am facing this nina_wrapper error 1 at 99% of compilation
Code:
[ 99% 3295/3298] Docs droiddoc: /home/...t/target/common/docs/doc-comment-check
FAILED: /bin/bash /home/suvam/rr/out/target/common/docs/doc-comment-check-timestamp.rsp
frameworks/base/core/java/android/provider/Settings.java:3657: error 101: Unresolved link/see tag "android.provider.Settings.Global#KEY_SMS_BREATH" in android.provider.Settings.System
frameworks/base/core/java/android/widget/SeekBar.java:41: error 101: Unresolved link/see tag "ProgressBar#setMax(int)" in android.preference.CustomSeekBarPreference
DroidDoc took 345 sec. to write docs to /home/suvam/rr/out/target/common/docs/doc-comment-check
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
As per this page (http://stackoverflow.com/questions/36733124/failed-to-make-the-source-of-android-6-0), you should check which JDK version you are building with. I've never seen this type of error, so you may just want to google it a bit further, if the JDK version doesn't help. Looks like you are making a lot of progress though!
jisoo said:
As per this page (http://stackoverflow.com/questions/36733124/failed-to-make-the-source-of-android-6-0), you should check which JDK version you are building with. I've never seen this type of error, so you may just want to google it a bit further, if the JDK version doesn't help. Looks like you are making a lot of progress though!
Click to expand...
Click to collapse
Checked. My jdk version is 1.8 as required for android 7
Resynced and used brunch DeviceCodeName and got this error
Code:
Building Kernel Config
make CFLAGS_MODULE="-fno-pic" -C kernel/meizu/m2note O=/home/suvam/rr/out/target/product/m2note/obj/KERNEL_OBJ ARCH=arm64 CROSS_COMPILE="/home/suvam/rr/prebuilts/misc/linux-x86/ccache/ccache aarch64-linux-androidkernel-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= los14_m2note_defconfig
make[1]: Entering directory '/home/suvam/rr/kernel/meizu/m2note'
HOSTCC scripts/basic/fixdep
/bin/sh: 1: ccache: not found
scripts/Makefile.host:118: recipe for target 'scripts/basic/fixdep' failed
make[3]: *** [scripts/basic/fixdep] Error 127
/home/suvam/rr/kernel/meizu/m2note/Makefile:424: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/suvam/rr/kernel/meizu/m2note'
vendor/cm/build/tasks/kernel.mk:283: recipe for target '/home/suvam/rr/out/target/product/m2note/obj/KERNEL_OBJ/.config' failed
make: *** [/home/suvam/rr/out/target/product/m2note/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....
It took approx 4 hours and then the compilation terminated.
Really hopeless now
*UPDATED*
resynced the repo and the device kernel and used brunch devicecode command and got this out of memory error and asked me to increase my heap size. How much should I set the heap size to ? I am having 6gb ram and current heap size is 3gb (by using java -Xmx 3072m)
I have attached the log file
Sync app email
Hi, i have installed on my Samsung s3 i9300 a resurrection remix but my app "aquamail" don't synchronizes in background.
When i update manually, it works regularly.
Please, can you help me?. :crying:
Thank's
mariorolex said:
Hi, i have installed on my Samsung s3 i9300 a resurrection remix but my app "aquamail" don't synchronizes in background.
When i update manually, it works regularly.
Please, can you help me?. :crying:
Thank's
Click to expand...
Click to collapse
Can someone help me?
mariorolex said:
Can someone help me?
Click to expand...
Click to collapse
Does anyone else have my own problem?. :crying::crying::crying:
Suvam Mondal said:
*UPDATED*
resynced the repo and the device kernel and used brunch devicecode command and got this out of memory error and asked me to increase my heap size. How much should I set the heap size to ? I am having 6gb ram and current heap size is 3gb (by using java -Xmx 3072m)
I have attached the log file
Click to expand...
Click to collapse
Reduce jack threads if you don't have at least 8GB free ram.
How do you solve Unresolved link/see tag error?

[HELP] LineageOS 14.1 Development

Hi. I am building LineageOS 14.1 for Huawei P8 Lite and used this tutorial: https://github.com/masterdoctor/Lin...i/LineageOS-|-Build-Tutorial-|-Huawei-P8-Lite
Done everything in the tutorial, everything looked fine until the build step. From that moment, I was like in "hell".
"croot" and "mka" commands didn't work, if I would've type them and enter it would say "unknown command" and recommended me a list of apps with a "similar" command.
Make worked, but after 3 minutes something about Ninja wrapper or builder error 1. I got a way to skip that, putting something in .bashrc to disable Ninja Wrapper.
Again tried, still no sign of "mka" or "croot" that they work, still stucked just with make.
Finnaly, I really got a hope, the process was longer than 3 minutes, I waited 20-30 minutes but stuck again with an error : :crying:
make: *** No rule to make target '/.txt', needed by '/root/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
[email protected]:~/android/system#
That is all what I got. Searched again on google now for this error and found a "fix" and ran this command to build : "make update-api && make -j4".
After again somewhere between 20-30 minutes got even more errors:
make: *** No rule to make target '/.txt', needed by '/root/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
make: *** Waiting for unfinished jobs....
Checking API: checktestapi-current
[email protected]:~/android/system#
I want to mention that I am using Ubuntu 16.04 64 Bit and that I did not used ccache, beacuse I didn't had too much space left.
May I done something wrong? I didn't install something? I missed something? Is there a fix for this?
I will be very thankful is someone helps me:good:
Thanks in advance!
Hi, I'm very sorry but the guide was incorrect.
Please do not use that guide.

Categories

Resources