This repository was archived by the owner on Feb 25, 2025. It is now read-only.
fuchsia: Convert legacy permutations to build flag #20647
Merged
+134
−546
Conversation
This file contains hidden or 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
dreveman
approved these changes
Aug 19, 2020
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/flutter
that referenced
this pull request
Aug 20, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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
These build permutations exist in order to create fuchsia artifacts that don't contain any legacy pre-embedder render code. However we don't need both permutations within the same build, so a build flag is much simpler than the template.
Related Issues
https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=53847
Tests
Tested both --legacy and --no-legacy built artifacts on workstation and internal builds.