You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Generate Aapt2 .flata archives on Nuget Restore. #2101
To help speed up initial build times we should investigate generating the aapt2 flata archives for support library components when the components are restored.
We should also look again and ways we can cache these archives (with the appropriate aapt2 version) so that they can be reused across a number of projects.
One way would be to run a target after Restore target. However, that would make the restore itself slower and could be considered a regression.
Alternatively, we can have the IDEs invoke this after restore is complete, with the same caveats as the Xamarin.Build.Download: if the process hasn't finished by the time the Build runs, it will be done there and then. (causing a slow-ish build the first time).
Using the same nuget package location would ensure it's properly versioned (i.e. a %userprofile%\.nuget\packages\xamarin.android.support.v4\27.0.2.1\obj\[BUILD_TOOLS_VERSION]), so that if users clean the nuget cache, those go away too (with nuget locals all -clear).
Activity
dellis1972 commentedon Sep 13, 2018
Need to figure out which Nuget target to hook into for this to work.
kzu commentedon Nov 8, 2018
One way would be to run a target after
Restoretarget. However, that would make the restore itself slower and could be considered a regression.Alternatively, we can have the IDEs invoke this after restore is complete, with the same caveats as the Xamarin.Build.Download: if the process hasn't finished by the time the Build runs, it will be done there and then. (causing a slow-ish build the first time).
Using the same nuget package location would ensure it's properly versioned (i.e. a
%userprofile%\.nuget\packages\xamarin.android.support.v4\27.0.2.1\obj\[BUILD_TOOLS_VERSION]), so that if users clean the nuget cache, those go away too (withnuget locals all -clear).dellis1972 commentedon Sep 24, 2019
I'm going to close this issue as its probably not going to help