I'm trying to customize the AOSP, And After compiled success once, I changed some selinux rule due to Android SElinux implementation <https://source.android.com/security/selinux/implement#steps>, And after that, I turn into AOSP root directory and run m, It indeed find some diff and seems compiled a new boot.img(due to time it generated), But After I flash it with fastboot flashall -w the dmesg still showing the avc sepolicy failed which I was just added
So the question is Am I doing wrong with the routine? Or Is there any mechanism I was ignored? If that What should I do?(Now I'm *m clean* and recompile all with *m* and problem gone, But it just takes hours) PS: I've found the policy.conf file under /out /target/product/marlin/obj/ETC/sepolicy_neverallows_intermediates and it sync with what I changed? -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/cfa4dd5b-41a7-44ac-8fe8-78db1453ea21%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
