[OnePlus 3 ROMs, Kernels, Recoveries, & Other Devel] salatiel:
Hi guys, i know that probably this is not the right place, but maybe someone here can help. Why is it so hard to compile cm13 for oneplus 3?

I've been compiling cyanogen for a while, since cm11, cm12, cm12.1 and even cm13 for hammerhead. But a few seeks ago i got a op3 and i am trying to

compile cm13 for it but i always get errors.

First time the error was about:

ThemeMixEntryColumns cannot be resolved to a variable

So i found here on xda that i should revert the commit '6abe369faa49d1e219d2c0456428be9d73d8442'

I dont know why should i revert a commit ( is cm13 repository broken? ), anyway i did that and got another error , now on messaging app:

packages/apps/Messaging/src/com/android/messaging/ui/conversation/ConversationMessageView.java:82: error: package com.cyanogen.ambient.ridesharing.core does not exist
import com.cyanogen.ambient.ridesharing.core.RidesharingContract;
... ^
packages/apps/Messaging/src/com/cyanogenmod/messaging/util/RidesharingUtil.java:10: error: cannot find symbol
import com.cyanogen.ambient.common.api.ComponentNameResult;
... ^
symbol: class ComponentNameResult
location: package com.cyanogen.ambient.common.api
packages/apps/Messaging/src/com/cyanogenmod/messaging/util/RidesharingUtil.java:13: error: package com.cyanogen.ambient.ridesharing does not exist
import com.cyanogen.ambient.ridesharing.RideSharingApi;
...

so i dug around and removed the ridesharing commits from messagind app, and when i finally thought that it would compile i get this:

build/tools/generate-notice-files.py /VMs/tmp/system/target/product/oneplus3/obj/NOTICE.txt /VMs/tmp/system/target/product/oneplus3/obj/NOTICE.html
"Notices for files contained in the filesystem images in this directory:" /VMs/tmp/system/target/product/oneplus3/obj/NOTICE_FILES/src
Combining NOTICE files into HTML
Combining NOTICE files into text
Installing recovery patch to system partition
Warning: could not find SYSTEM/build.prop in <built-in function zip>
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 55, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 51, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File "/data/home/build/android/branches/cm13/build/tools/releasetools/common.py", line 1537, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
File "/data/home/build/android/branches/cm13/build/tools/releasetools/common.py", line 1210, in ComputePatch
p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/data/home/build/android/branches/cm13/build/tools/releasetools/common.py", line 105, in Run
return subprocess.Popen(args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
build/core/Makefile:1074: recipe for target '/VMs/tmp/system/target/product/oneplus3/system/bin/install-recovery.sh' failed
make: *** [/VMs/tmp/system/target/product/oneplus3/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/data/home/build/android/branches/cm13'

#### make failed to build some targets (01:36:55 (hh:mm:ss)) ####

and from here i have absolutely no idea how to proceed. Any help ?