Repository navigation
Add Windows, and Linux as TargetPlatforms #31366
Copy link
Copy link
Closed
Labels
a: desktopRunning on desktopRunning on desktopframeworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.platform-linuxBuilding on or for Linux specificallyBuilding on or for Linux specificallyplatform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallyplatform-windowsBuilding on or for Windows specificallyBuilding on or for Windows specifically
Description
Activity
- addedplatform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallyplatform-windowsBuilding on or for Windows specificallyBuilding on or for Windows specificallyplatform-linuxBuilding on or for Linux specificallyBuilding on or for Linux specificallya: desktopRunning on desktopRunning on desktop
on Apr 20, 2019 - addedtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.and removedtoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
on Jul 26, 2019 - changed the title
[-]Add macOS, Windows, and Linux as TargetPlatforms[/-][+]Add Windows, and Linux as TargetPlatforms[/+]on Dec 4, 2019 - added a commit that references this issue
on Mar 3, 2020 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 -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 17, 2021
Metadata
Metadata
Assignees
Labels
a: desktopRunning on desktopRunning on desktopframeworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.platform-linuxBuilding on or for Linux specificallyBuilding on or for Linux specificallyplatform-macosBuilding on or for macOS specificallyBuilding on or for macOS specificallyplatform-windowsBuilding on or for Windows specificallyBuilding on or for Windows specifically
Currently, running on desktop requires overriding the default target platform using a debug flag. From previous discussions, before we add desktop platforms to
TargetPlatformwe need to audit the framework for a list of significant changes we would want to make for desktop (e.g., button and text field metrics, scrollbar behaviors, etc.), and have a plan to burn that last down fairly quickly. The goal is to minimize the amount of time where behaviors are changing, so there's not time for people to start depending on behaviors that are then changed.Filling to track that overall project.
CC @gspencergoog