I was trying to figure out why google/flutter-desktop-embedding#599 was running the linked App.framework's AOT code instead of just failing outright, and realized that we're not actually doing anything in the macOS version of FlutterDartProject that would control the AOT code being used (i.e., the equivalent of the iOS FlutterDartProject's settings.application_library_path code).

I believe this means it's impossible to run two different AOT compilations in the same app in an add-to-app scenario, for instance.

@chinmaygarde What's the right way to do the equivalent of application_library_path via the embedder API? vm_snapshot_data? (And if so, why is this currently working at all?)

/cc @jonahwilliams maybe you know since you wired this up.