search

minimal-manifest-twrp / platform_manifest_twrp_aosp

Minimal manifest for building TWRP for devices shipped with Android 10+
298 stars 273 forks source link

ninja no work to do #47

Open CaptialState opened 5 months ago

CaptialState commented 5 months ago

On building twrp for device air (Redmi 13C 5G) running mka vendorbootimage the vendor_boot.img is not generated in the out/ directory, Upon checking the logs it showed

ninja: no work to do.

So where did i go wrong? Here are: logs devicetree

Athwale commented 1 month ago

Same problem, but different repo: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/issues/119 Have you been able to find any information? I have been trying to debug this for a while, but fruitlessly.

CaptialState commented 1 month ago

@Athwale Hello there, It has been a while and i've asked about this particular problem on several repositories, As far as i know this only happens to mediatek processor and i theorize that it was due to proprietary blobs. I have so far not found any fixes for this and gave up

Athwale commented 1 month ago

The easiest thing here would be if a twrp devel tried this out with the knowledge of how the internals work. I suspect that the repositories maybe are broken and some files are missing. Maybe. I found out that the variable in the Makefile that tells the builder to make a recovery image is not set to true. I do not know why though. If you set it to true manually, the compiler complains that it can not find some files.

Have you found out any options or environment variables that would produce more verbose output for debugging?