Android.mk: Support android_4.x build #70
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update 2.4.0.1 is only available under android_4.x and android_2.3 folders.
To provide the choice during AOSP inline compilation,
a new variable is available and can be set into BoardConfig
VIPER4ANDROID_FOLDER := android_4.x-5.x
VIPER4ANDROID_FOLDER := android_4.x
By default android_4.x will be used to compile ViPER4Android except for AOSP API <= 9
that will use android_2.3