flutter/dev/integration_tests/link_hook/hook/build.dart
Martin Kustermann 3a83e43ede
Make flutter_tools use newest package:{native_assets_builder,native_assets_cli,native_toolchain_c} (#158214)
Almost all of the code is just adopting to changes to the APIs of
`package:native_assets_builder`, `package:native_assets_cli` and
`package:native_toolchain_c`

There's only two semantic changes

* Removes a test that checks for a verification error if a build hook
produces a static library if the preferred linking mode is dynamic:
=> The test is written in a very hacky way. By monkey patching the build
config.json that flutter build actually made. This monkey patching
relies on package:cli_config which is now no longer used.
=> The actual code that checks for this mismatch lives in
dart-lang/native repository and is tested there. So there's really no
need to duplicate that.

* The `package:native_assets_builder` no longer knows about code assets.
This is something a user of that package (e.g. flutter tools) adds. Now
the dry-run functionality will invoke build hooks who produce code
assets without an architecture.
=> The `package:native_assets_builder` used to expand such a code asset
to N different code assets (one for each supported architecture)
=> This logic was now moved to flutter tools. => In the near future
we're going to this dry-run complexity, which will then also get rid of
this uglyness (of expanding to all archs of an OS).
2024-11-06 14:12:34 +01:00

50 lines
1.9 KiB
Dart

// Copyright 2014 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
import 'package:logging/logging.dart';
import 'package:native_assets_cli/code_assets.dart';
import 'package:native_assets_cli/code_assets_builder.dart';
import 'package:native_toolchain_c/native_toolchain_c.dart';
void main(List<String> args) async {
await build(args, (BuildConfig config, BuildOutputBuilder output) async {
final String assetName;
if (config.linkingEnabled) {
// The link hook will be run. So emit an asset with a name that is
// not used, so that the link hook can rename it.
// This will ensure the test fails if the link-hooks are not run
// while being reported that linking is enabled.
assetName = 'some_asset_name_that_is_not_used';
} else {
// The link hook will not be run, so immediately emit an asset for
// bundling.
assetName = '${config.packageName}_bindings_generated.dart';
}
final String packageName = config.packageName;
final CBuilder cbuilder = CBuilder.library(
name: packageName,
assetName: assetName,
sources: <String>[
'src/$packageName.c',
],
dartBuildFiles: <String>['hook/build.dart'],
);
final BuildOutputBuilder outputCatcher = BuildOutputBuilder();
await cbuilder.run(
config: config,
output: outputCatcher,
logger: Logger('')
..level = Level.ALL
..onRecord.listen((LogRecord record) => print(record.message)),
);
final BuildOutput catchedOutput = BuildOutput(outputCatcher.json);
output.addDependencies(catchedOutput.dependencies);
// Send the asset to hook/link.dart or immediately for bundling.
output.codeAssets.add(
catchedOutput.codeAssets.single,
linkInPackage: config.linkingEnabled ? 'link_hook' : null,
);
});
}