Distinguish between usage during AOSP build, as system compiler or as an app asset #16
Assignees
Labels
Comments
schrnz
added a commit
to Project-ARTist/art
that referenced
this issue
May 23, 2018
* detect whether we are compiling as a part of an AOSP build, during system boot or through ArtistGui: close Project-ARTist/meta#16 * support for compiling the boot.oat/art images: close Project-ARTist/meta#17 * support for compiling the systemserver: close Project-ARTist/meta#2 * deactivated the filesystem helper for the system compilation scenario due to the very restrictive SELinux policy for dex2oat (cherry picked from commit c137305)
partipan-dot
pushed a commit
to Project-ARTist/art
that referenced
this issue
Sep 8, 2019
* detect whether we are compiling as a part of an AOSP build, during system boot or through ArtistGui: close Project-ARTist/meta#16 * support for compiling the boot.oat/art images: close Project-ARTist/meta#17 * support for compiling the systemserver: close Project-ARTist/meta#2 * deactivated the filesystem helper for the system compilation scenario due to the very restrictive SELinux policy for dex2oat
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Distinguishing whether the current compilation is happening as a part of the AOSP build (creating the initial
boot.oatandboot.art), during system boot (first & after OS upgrade) or at regular system runtime for app compilation (the ArtistGui path) is required for the filesystem helper to provide the appropriate paths (see TODO in this commit that closed Project-ARTist/ARTist#16). While it is obvious that the paths on an AOSP build machine and on the actual Android device differ, we also need to differentiate between system compiler and ArtistGui compilation because at boot time not all directories are accessible and we cannot assume that ArtistGui and its folder structure is created already.Affected Projects
The text was updated successfully, but these errors were encountered: