[native_assets_builder] `build.dart` -> `hook/build.dart` (#1018)

* https://github.com/dart-lang/native/issues/823

Notes:

* Should keep existing toplevel `build.dart` scripts working by trying both `hook/build.dart` and `build.dart`.
* Does not migrate the examples yet, so that we don't have to do `breaking-change` is true in the ci.
   * Will do this after rolling into Dart.
* `native_toolchain_c` had a `this.dartBuildFiles = const ['build.dart'],`. Updating that to `hook/build.dart` would not work for unmigrated scripts, because files listed as dependencies that don't exist will also trigger a rebuild, e.g. it is considered deleting a file. It would also break on any kind of invocation from `hook/link.dart`. So, I've removed the default value for now. It's not pretty though. Ideas @mosuem?
43 files changed
tree: 9152c39f06a6da86d2af7adc219cd55819523b39
  1. .github/
  2. pkgs/
  3. AUTHORS
  4. CONTRIBUTING.md
  5. LICENSE
  6. README.md
README.md

Coverage Status

Overview

This repository is home to Dart packages related to FFI and native assets building and bundling.

Packages

PackageDescriptionVersion
ffiUtilities for working with Foreign Function Interface (FFI) code.pub package
ffigenGenerator for FFI bindings, using LibClang to parse C, Objective-C, and Swift files.pub package
jniA library to access JNI from Dart and Flutter that acts as a support library for package:jnigen.pub package
jnigenA Dart bindings generator for Java and Kotlin that uses JNI under the hood to interop with Java virtual machine.pub package
native_assets_builderThis package is the backend that invokes top-level build.dart scripts.pub package
native_assets_cliA library that contains the argument and file formats for implementing a native assets CLI.pub package
native_toolchain_cA library to invoke the native C compiler installed on the host machine.pub package

Publishing automation

For information about our publishing automation and release process, see https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

For additional information about contributing, see our contributing page.