@andrelam could you add this unzip package to the prerequsites at beginning of your script ?
Nice one thank you. /srv/src/PIE is the source directory
I know))))))))))))))
Now I’m chipping away at the build errors 
I will crack this build!
Can anyone help with this error regarding a live display library error?
I’ve search and found this article about commenting out the library in teh device.mk file but it had no effect. I have no further directories or files in /srv/src/PIE/out/target/product/clover/
thanks
Sorry, can’t help, but could you please do a favor and open a new post for build help. This post here is a howto. Thx
maybe you should add this repository https://github.com/vanhoopstallion/android_device_xiaomi_clover-oss
That is his repository 
its not included in his manifest, so i think he also not copied it with git clone
I will update the script when i have time, it’s out of sync with the latest /e/ docker file.
2 Likes
Unless specific execution parameters need to changed I think this way is not needed any longer. I was able to build an unsupported device by simply placing the local manifest for it in a folder that is passed to docker as path like so
-v "/opt/e-build/local_manifests:/srv/local_manifests:delegated"
This is picked up as with a local (non-docker) run, and as all device customization goes into this file nothing else is needed.
Things are probably different if you are a developer and need to do changes in the main sources, but for simply building an unsupported device where device-tree repositories are available this does the trick for me.
possibly a silly question:
Your HowTo is about building /e/. It is my understanding that /e/ is with no google code, but MicroG instead. In Github I found vendor, device and kernel files for ‘my’ device (Samsung A3 a3ultexx). How can I verify that these files are usable for building /e/, means with no google code?
Thank you
You can’t. The proprietary files are always critical, but you can’t build without them.
@harvey186: thank you
Thus is solved I think. Or? ?
What did you write in the terminal ?
What’s in your manifest roomservice.xml?
1 Like
And your sources have ‘lineage-16.0’ as default branch? ?
Your default branch on github is lineage17.1, specify revision="lineage-16.0" or make lineage-16.0 default on github.
I don’t know if it matters, but shouldn’t “redmi” in paths be “xiaomi” ?
1 Like