• stuartmorgan's avatar
    Fix local engine use in macOS plugins (#140222) · 24e06232
    stuartmorgan authored
    Currently podhelper.rb will always point plugin builds at the cached engine artifacts, even when using `--local-engine`. In most cases this is fine, since when the final build actually runs it will be using the engine bundled into the app build, which will be the correct local engine build. When trying to test a local engine build with API additions against a local plugin modified to use those additions to ensure that they are working as expected, however, compilation will fail, because the new APIs won't be present in the plugin build.
    
    This fixes that for macOS, and adds a TODO for iOS (which is more complicated to fix due to the host vs target build distinction).
    
    macOS portion of https://github.com/flutter/flutter/issues/132228
    24e06232
Name
Last commit
Last update
..
a11y_assessments Loading commit data...
automated_tests Loading commit data...
benchmarks Loading commit data...
bots Loading commit data...
conductor Loading commit data...
customer_testing Loading commit data...
devicelab Loading commit data...
docs Loading commit data...
forbidden_from_release_tests Loading commit data...
integration_tests Loading commit data...
manual_tests Loading commit data...
missing_dependency_tests Loading commit data...
snippets/config Loading commit data...
tools Loading commit data...
tracing_tests Loading commit data...
README.md Loading commit data...
analysis_options.yaml Loading commit data...