Android build: Use aapt2 instead of aapt to generate R.txt file |
|
Issue descriptionThe R.txt file generated for android_resources targets (through build/android/gyp/process_resources.py) uses 'aapt' instead of 'aapt2' because the latter doesn't support the --output-text-symbols option when doing 'aapt2 compile' (it does when doing 'aapt2 link' though). However, 'aapt' is deprecated and will be removed in the future, and an upcoming version of 'aapt2' will support this option during compilation. This is to track the issue and fix it once we roll the Chromium build to a newer Android SDK that has the right tool.
,
Mar 9 2018
I'd be surprised if aapt went away since aapt2 has no where near the "dump" capabilities. Makes sense to use aapt2 for R.txt if it does eventually support it though.
,
Mar 9 2018
I've been told by Android SDK developers that 'aapt' will be deprecated "soon", hence this issue. There is no rush though :) |
|
►
Sign in to add a comment |
|
Comment 1 by digit@chromium.org
, Mar 9 2018