Repository navigation
[native_assets] Use kernel concatenation instead of passing in asset-mapping into kernel compilation #146270
Description
Activity
The kernel kernel-file compilation currently uses the frontend_server with a single-shot invocation from the
KernelSnapshotTarget.Some implementation considerations:
- We can either run the frontend_server twice as a process invocation, or keep the process running after the dart compilation and then shut it down after native assets compilation to kernel. Keeping the process running would require more coordination between different
Targets. - We can either chose to only do separate kernel file compilation in release (AOT) builds, or do it both for JIT and AOT. Doing it differently in JIT/AOT means more conditionals in lib/src/build_system/targets/, doing it single-shot in JIT might be more performant though.
- We can either run the frontend_server twice as a process invocation, or keep the process running after the dart compilation and then shut it down after native assets compilation to kernel. Keeping the process running would require more coordination between different
- added a commit that references this issue
on Apr 25, 2024 This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on May 21, 2024
We'd like to support adding new assets in link hooks (#146263).
Use cases:
Because the link hooks are run after kernel compilation, that will require using kernel concatenation instead of passing in the native asset mapping before kernel compilation.
Dart tracking issue: