Originally Posted by jimmcghee
<project name="CyanogenMod/android_device_bn_encore" path="device/bn/encore" remote="github" />
<project name="CyanogenMod/android_kernel_bn_encore" path="kernel/bn/encore" remote="github" revision="encore-omap3-3" />
Should have posted them the first time.
Gosh, that was fast!!!
You need the proprietary files (props).
This error is sort of my fault. We had a broken build because of a broken link to the proprietary files. I fixed it so that it doesn't build if there are no props but it also causes difficulties when setting up a new build environment. I don't know of a good solution for this. I guess we could edit the build it yourself wiki page. Other devices just continue to make broken builds even if the props are missing.
You need the vendor/bn/encore proprietary files directory. You can generate it by running extract-files.sh from the device/bn/encore directory. This require you have an NC with cm on it plugged in via usb. Or, you can run unzip-files.sh and point it to a current cm zip file. Alternatively, you can find a repo with proprietary_vendor_bn/tree/cm-10.2 on github. I'm not sure if I should post the name of the secret (public) github repo that has all the cm props on it. Think Elmo and Oscar the Grouch.