From 45bf790926da592f4f94bd9a6eec76ff7d91d9c1 Mon Sep 17 00:00:00 2001 From: stuartmorgan Date: Sun, 27 Jan 2019 12:52:17 -0800 Subject: [PATCH 1/2] Add a warning about binaries to library README Call out the requirement that the library and the Flutter application must be build with the same version, since some people have started distributing binary versions apparently without being aware of this. --- library/README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/library/README.md b/library/README.md index 79329f705..fdfa9d9cc 100644 --- a/library/README.md +++ b/library/README.md @@ -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 releasese 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 From ba67b4bb107ef3bd08e37b789eca9485226abe67 Mon Sep 17 00:00:00 2001 From: stuartmorgan Date: Mon, 28 Jan 2019 11:03:21 -0800 Subject: [PATCH 2/2] Typo fix --- library/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/README.md b/library/README.md index fdfa9d9cc..98447350f 100644 --- a/library/README.md +++ b/library/README.md @@ -19,7 +19,7 @@ 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 releasese is that you *must* use the same version of Flutter to build +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.)