I'm not sure anyone is using the systemtarball functionality anymore,
especially with the lack of selinux as you've discovered.
Generally we put the prebuilt APKs as inputs into the Android build, since
they may be modified and transformed by the build (uncompress shared libs,
strip dex files,
It sounds like you're using at least some of the code from Oreo, but didn't
take the repo manifest updates that added entries to put those
back into place. Which may mean that you're also missing new projects, or
still have projects that have been removed as well.
- Dan
On Wed, Sep 19, 2018 at
Download the source and set up your machine as described on
https://source.android.com/setup/build/requirements
Basically, do everything up to the "lunch" step, then use "tapas" instead:
$ tapas LatinIME arm64
$ m
The APK will be
in
On Linux, build/envsetup.sh is a symlink to make/envsetup.sh so you can
still use:
. build/envsetup.sh
Are you sure you are in the top directory of your sandbox when you issued
the ". build/envsetup.sh" ?
"lunch 39" might not be a valid lunch target. Try using another lunch
target name
Hi,
I'm trying to build AOSP od macOS. After dealing with few problem, I'm
having a hard time with (I hope) the last one. Please give me some advise:
[ 0% 53/69590] //external/selinux/checkpolicy:checkpolicy yacc
policy_parse.y [darwin]
FAILED:
Hello yall,
i tried to create a system tarball to add some apk's in other build jobs.
but the created tarballs have no selinux context inside. a look into
build/tools/mktarball.sh shows, that tar is used without --selinux
parameter.
If i put the content from that tarball to my system
I am also trying to develop LatinIME but there is less understanding to
develop it.
Thanks,
On Monday, August 27, 2018 at 9:40:02 PM UTC+5:30, Vedant Roy wrote:
>
> I am trying to build the Latin IME input method.
>
> The source code can be found here:
>
