Skip to content

[et] et build --config documentation #156591

Closed
flutter-team-archive/engine
#56324

Description

@dcharkes

I'm trying to adopt et into my workflow instead of using gn/ninja. So far it's great (RBE works out of the box 🎉)!

While trying to convert my Android workflows I noticed that a lot of android configs are missing, but some of them show up under ci/. Also some are duplicated android_debug_arm64 and ci/android_debug_arm64. The help provides no information what the difference between these are.

Also, et seems to accept configurations not listed in the --config flag: For example for on my M1 host_debug_unopt_arm64.

Side note: there seems to be some overlap between the gn directories produced and the value for the config flag, but without ci/?

I have the following suggestions to improve the situation:

  • Add documentation
  • Provide an exhaustive list in help, without duplicates.

Activity

  1. added
    in triagePresently being triaged by the triage team
    and removed
    in triagePresently being triaged by the triage team
    on Oct 14, 2024
  2. added
    P3Issues that are less important to the Flutter project
    on Oct 14, 2024
  3. self-assigned this
    on Oct 31, 2024
  4. github-actions commented on Nov 16, 2024

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  5. locked as resolved and limited conversation to collaborators on Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P3Issues that are less important to the Flutter projecte: engine-toolEngine-specific tooling (i.e. `tools/engine_tool`).team-engineOwned by Engine teamtriaged-engineTriaged by Engine team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions