Allow overridable configure arguments for AL build #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Alternative solution to #125. When
bash configuregets duplicated arguments, it uses the last given argument. To take advantage of this, theadditional_configure_optionsis moved last so that any passed configure arguments through gradle can override any prior static configure arguments for AL buildsRelated issues
This also solves this issue #125
Motivation and context
To allow a way to dynamically set vendor url config args for AL builds
How has this been tested?
Through internal infrastructure
Platform information
Additional context
n/a