//build/android/generate_gradle.py should use autoninja
Reported by
hvostik....@gmail.com,
Jan 18 2018
|
|||||
Issue descriptionI`m already checked out chromium sources, build APK using ninja. Now I`m trying to generate project for Android Studio using build/generate_gradle.py script. It took 16GB (100%) of my RAM and continuing using SWAP which also tool 100% of 16GB. Seems like a bug in the script, memory is full and progress of generating (like [100/16000]) does not move. So this script as I think doesnt free memory after generating every file for Android Studio project.
,
Jan 18 2018
,
Jan 18 2018
CC'ing OWNERS for thoughts here.
,
Jan 18 2018
The majority of what the script does is build things via ninja. You might try running with --verbose and seeing which targets are being built. Maybe building them first not via the script would go better?
,
Jan 18 2018
Already did it with "verbose" flag. It shows just progress like [125/16000] ACTION/STAMP/CXX whatever. Also built target APK before running this script.
,
Jan 18 2018
Another thing to try: pass --target //chrome/android:chrome_public_apk That will have it generated fewer targets (assuming you mainly care about the main apk)
,
Jan 18 2018
Unfortunately it's a known issue, see issue 799954
,
Mar 3 2018
I've found a solution. The problem is the ninja j parameter, the thread count has been set to 1000. Just set the parameter to 50 in the script and it will work. https://groups.google.com/a/chromium.org/d/msg/chromium-dev/NW8MdjXy5yI/1YncKHUlBQAJ
,
Jan 10
Issue moved from a project with a different set of status labels. "New" is not a supported status in /p/chromium, so these ended up in a black-hole.
,
Jan 10
I believe the proper fix here is to make it use autoninja.
,
Jan 14
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by hvostik....@gmail.com
, Jan 18 2018