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/
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
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?