Skip to content

Add a warning about binaries to library README #250

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 28, 2019
Merged

Add a warning about binaries to library README #250

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
45bf790
Add a warning about binaries to library README
stuartmorgan Jan 27, 2019
ba67b4b
Typo fix
stuartmorgan Jan 28, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions library/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,12 @@ for now there is no equivalent to `flutter create`.
There are currently no binary releases of the libraries. While a more
Flutter-like model of using an SDK containing pre-compiled binaries is likely
to be supported in the future, for now you must build the library from source.
(**Note:** You may be tempted to pre-build a generic binary that can run any
Flutter app. If you do, keep in mind that the primary reason there are no
binary releases is that you *must* use the same version of Flutter to build
`flutter_assets` as you use to build the library. If you later upgrade Flutter,
or if you distribute the binary version to other people building their
applications with different versions of Flutter, it will break.)

Once you build the library for your platform, link it into your build using
whatever build system you are using, and add the relevant headers (see
Expand Down