Skip to content

Add additional interpolated values to custom devices commands #164454

Closed

Description

@vially

Use case

Flutter's support for custom devices makes it possible for (out-of-tree) custom embedders to hook into and integrate with the flutter run command.

However, this integration could be further improved if the flutter tool provided some additional (string interpolated) values that are typically required by custom devices and embedders:

  • path to the ICU data file
    The flutter tool takes care of copying the ICU data file to the right location for each of the officially supported platforms and devices during the build process. However, that's not the case for custom devices and embedders so they need a way to locate the ICU data file.
  • engine revision
    Similar to the above, custom devices and embedders need to manually manage the engine library (e.g.: libflutter_engine.so). Providing the engine version through the custom-device commands would avoid the need for some heuristics on the custom embedder side and should make it easier to keep it in sync with the flutter tool.
  • build mode
    Currently custom devices only support the debug build mode, but hopefully this is going to change in the future (Add support for profile and release run modes for custom devices #164228)

Proposal

Make the following (additional) string interpolated values available to the postBuild and runDebug custom device commands:

  • ${icuDataPath}
  • ${engineRevision}
  • ${buildMode}

Activity

  1. added
    in triagePresently being triaged by the triage team
    toolAffects the "flutter" command-line tool. See also t: labels.
    c: proposalA detailed proposal for a change to Flutter
    team-toolOwned by Flutter Tool team
    and removed
    in triagePresently being triaged by the triage team
    on Mar 3, 2025
  2. bkonyi commented on Apr 8, 2025

    @bkonyi
    Contributor

    This isn't something we're going to be able to prioritize on our size given that we plan to do some refactoring to the tool in the future that would likely make this issue irrelevant. However, there's no timeline on those refactors, so we'd be willing to accept a simple PR with tests to resolve this if you're interested in contributing a fix.

  3. added
    P3Issues that are less important to the Flutter project
    triaged-toolTriaged by Flutter Tool team
    on Apr 8, 2025
  4. vially commented on Apr 8, 2025

    @vially
    ContributorAuthor

    @bkonyi Thank you for your reply. There is a pending pull-request that implements this at #164455.

  5. bkonyi commented on Apr 9, 2025

    @bkonyi
    Contributor

    Thank you for your reply. There is a pending pull-request that implements this at #164455.

    Ah sorry, I missed that there was PR linked here. Thank you!

  6. github-actions commented on Apr 24, 2025

    @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.

  7. locked as resolved and limited conversation to collaborators on Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectc: proposalA detailed proposal for a change to Flutterr: fixedIssue is closed as already fixed in a newer versionteam-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.triaged-toolTriaged by Flutter Tool team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions