Skip to content

Support 'flutter build' for desktop targets #30706

Closed

Description

@stuartmorgan-g

Tracks being able to flutter build for macOS, Windows, and Linux.

In the long term this would use the templates created by create (see #30703, #30704, and #30705), but shorter term—and also longer-term to support use cases other than flutter create, such as Add-to-App—it would be good to support pluggable build steps.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    platform-macosBuilding on or for macOS specifically
    platform-windowsBuilding on or for Windows specifically
    platform-linuxBuilding on or for Linux specifically
    on Apr 8, 2019
  2. stuartmorgan-g commented on Apr 8, 2019

    @stuartmorgan-g
    ContributorAuthor

    Any support we can provide for this in the short term is very valuable for the workflow of people trying out early stages of the desktop support, since if it's possible to do one-time setup of a pluggable build step, then once the project is set up manually, the edit-build-run/debug cycle in IDEs that support Flutter will work for free.

  3. self-assigned this
    on Apr 8, 2019
  4. stuartmorgan-g commented on May 9, 2019

    @stuartmorgan-g
    ContributorAuthor

    For macOS, things I'm aware of remaining within the scope of this bug:

    • Eliminate the need for name_output.sh
    • Finalize the copying of resources (e.g., standardizing on putting things in macos/Flutter/)
    • Finalize the name/location(s) of the script(s)/command(s) that Xcode invokes
  5. ammaratef45 commented on Jul 14, 2019

    @ammaratef45

    This is essential, I can't rely on a code that can't be built and delivered.

  6. added this to the milestone on Aug 13, 2019
  7. stuartmorgan-g commented on Aug 14, 2019

    @stuartmorgan-g
    ContributorAuthor

    I think given the plans around assemble and other related plans, we can just close this now. Originally I was leaving it open until the interactions were finalized, but the current state is that building works on all desktop platforms in an initial state. We'll be doing a lot of incremental changes/improvements, and it makes more sense to track those in individual bugs (which in fact is already happening) rather than a single large bug.

  8. github-actions commented on Aug 14, 2021

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

  9. locked as resolved and limited conversation to collaborators on Aug 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

a: desktopRunning on desktopplatform-linuxBuilding on or for Linux specificallyplatform-macosBuilding on or for macOS specificallyplatform-windowsBuilding on or for Windows specificallytoolAffects the "flutter" command-line tool. See also t: labels.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions