Skip to content
Prev Previous commit
Apply change request
  • Loading branch information
mosuem committed Feb 9, 2024
commit 746a74db71ca0013a519d652a976e7bdf8f23d2b
2 changes: 1 addition & 1 deletion pkgs/native_assets_builder/doc/protocol/v1.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Additionally, the convention is that an asset referenced from `lib/src/foo.dart`
A target specifies the operating system and architecture of the targeted platform of the application.

#### `build.dart`
If there are assets in a package which have to be "manually" bundled, i.e. they are not shipped as part of Dart or Flutter and are also not present on the target system by default, that package must define a `build.dart` script specifying these assets. This script takes as input information such as the target OS and architecture in a `build_config.yaml` file, and returns as output a list of assets to be bundled in a `build_output.yaml` file.
Any package which needs to access assets at runtime must define a `build.dart` script to specify these assets. If there are assets in a package which are not shipped as part of Dart or Flutter and also not present on the target system by default, those assets will be bundled into the final application by the Dart or Flutter SDK automatically. The `build.dart` script takes as input information such as the target OS and architecture in a `build_config.yaml` file, and returns as output a list of assets which can be accessed at runtime in a `build_output.yaml` file.

### `build_config.yaml`

Expand Down