Skip to content

Move desktop target platform artifacts out of host platform artifact directory. #38935

Open
0 of 1 issue completed
Open
Move desktop target platform artifacts out of host platform artifact directory.#38935
0 of 1 issue completed
Labels
P3Issues that are less important to the Flutter projecta: desktopRunning on desktopc: contributor-productivityTeam-specific productivity, code health, technical debt.c: tech-debtTechnical debt, code quality, testing, etc.team-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.triaged-toolTriaged by Flutter Tool team

Description

@jonahwilliams
jonahwilliams
opened on Aug 21, 2019

The debug desktop target platform is currently cohabitating with the host platform artifacts of the same name. The debug target platform artifacts should be moved to platform-debug to match the reset of the artifact repository.

This could be done via a soft transition by upload the artifacts to both directories, and then removing the old upload once the tool is updated.

Activity

  1. jonahwilliams
    added
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Aug 21, 2019
  2. jonahwilliams
    self-assigned this
    on Aug 21, 2019

  3. stuartmorgan-g commented on Jun 2, 2020

    @stuartmorgan-g
    stuartmorgan-g
    on Jun 2, 2020
    Contributor

    https://flutter-review.googlesource.com/c/recipes/+/3220

  4. jonahwilliams
    removed their assignment
    on Jun 9, 2020
  5. danagbemava-nc
    added
    a: desktopRunning on desktop
    on Sep 27, 2022
  6. gspencergoog
    assigned
    cbracken
    on Sep 29, 2022
  7. gspencergoog
    added
    P2Important issues not at the top of the work list
    on Sep 29, 2022

  8. cbracken commented on Sep 29, 2022

    @cbracken
    cbracken
    on Sep 29, 2022
    Member

    Deduped against #108756, which I'm working on right now.

  9. flutter-triage-bot
    added
    multiteam-retriage-candidate
    team-desktop
    triaged-desktop
    and removed
    triaged-desktop
    on Jul 7, 2023

  10. flutter-triage-bot commented on Jul 8, 2023

    @flutter-triage-bot
    flutter-triage-botbot
    on Jul 8, 2023

    This issue is assigned but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

  11. flutter-triage-bot
    added
    ⏳Bot is counting down the days until it unassigns the issue
    on Jul 30, 2023
  12. flutter-triage-bot
    unassigned
    cbracken
    on Jul 31, 2023

  13. 17 remaining items

  14. flutter-triage-bot
    removed
    triaged-desktop
    on Jun 7, 2024

  15. flutter-triage-bot commented on Jun 7, 2024

    @flutter-triage-bot
    flutter-triage-botbot
    on Jun 7, 2024

    The triaged-desktop label is irrelevant if there is no team-desktop label or fyi-desktop label.

  16. cbracken
    added a commit that references this issue on Jul 19, 2024

    Move !is_android to build_engine_artifacts declaration (#54006)

    5810b3f
  17. christopherfujino
    added
    triaged-toolTriaged by Flutter Tool team
    on Aug 9, 2024
  18. cbracken
    added 2 commits that reference this issue on Jan 23, 2025

    flutter_tools: flutter_tester is a host artifact

    727fbfd

    flutter_tools: flutter_tester is a host artifact

    cecb2c3
  19. github-merge-queue
    added a commit that references this issue on Jan 23, 2025

    flutter_tools: flutter_tester is a host artifact (#162047)

    1daa755
  20. Wasmund1
    added a commit that references this issue on Jan 24, 2025

    flutter_tools: flutter_tester is a host artifact (flutter#162047)

    c06845d

  21. bkonyi commented on Jun 30, 2025

    @bkonyi
    bkonyi
    on Jun 30, 2025
    Contributor

    @cbracken is this still a valid issue?

  22. cbracken commented on Jul 1, 2025

    @cbracken
    cbracken
    on Jul 1, 2025
    Member

    Yes. We should really not be building the desktop-specifc products like FlutterMacOS.framework or the Windows DLL as part of the host build. The host build should be host products that are used regardless of target -- e.g. the Dart SDK, flutter_tester, etc.

  23. bkonyi
    added
    tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.
    on Jul 7, 2025
  24. jmagman
    added
    c: contributor-productivityTeam-specific productivity, code health, technical debt.
    on Jan 22, 2026
  25. jmagman
    added a sub-issue on Apr 16, 2026

  26. jmagman commented on Apr 16, 2026

    @jmagman
    jmagman
    on Apr 16, 2026
    Member

    We should really not be building the desktop-specifc products like FlutterMacOS.framework or the Windows DLL as part of the host build. The host build should be host products that are used regardless of target -- e.g. the Dart SDK, flutter_tester, etc.

    I reopened #108756 to track the engine build rule work.

  27. zhongdaiqi
    added a commit that references this issue on Oct 9, 2026

    Move !is_android to build_engine_artifacts declaration (flutter-team-…

    89811b3
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 projecta: desktopRunning on desktopc: contributor-productivityTeam-specific productivity, code health, technical debt.c: tech-debtTechnical debt, code quality, testing, etc.team-toolOwned by Flutter Tool teamtoolAffects the "flutter" command-line tool. See also t: labels.tool-still-validIssues that have been deemed still valid as part of the Flutter Tools issue cleanup initiative.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