Fix ILLink running in incremental builds #77110
Conversation
Now that the new APICompat runs after all the compilation targets, this depends on in illink.targets isn't necessary anymore and fixes the incremental build issue. Regressed with 960e4d7 as the new APICompat doesn't run as post compiler target anymore but instead, as part of the `PrepareForRun` target. That caused the ILLink dependent target to always run, even if the compiler didn't run and the inputs/outputs didn't change.
ghost
added
the
linkable-framework
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsNow that the new APICompat runs after all the compilation targets, this depends on in illink.targets isn't necessary anymore and fixes the incremental build issue. Regressed with 960e4d7 as the new APICompat doesn't run as post compiler target anymore but instead, as part of the cc @smasher164
|
|
Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @sbomer, @joperezr Issue DetailsNow that the new APICompat runs after all the compilation targets, this depends on in illink.targets isn't necessary anymore and fixes the incremental build issue. Regressed with 960e4d7 as the new APICompat doesn't run as post compiler target anymore but instead, as part of the cc @smasher164
|
Now that the new APICompat runs after all the compilation targets, this depends on in illink.targets isn't necessary anymore and fixes the incremental build issue.
Regressed with 960e4d7 as the new APICompat doesn't run as post compiler target anymore but instead, as part of the
PrepareForRuntarget. That caused the ILLink dependent target to always run, even if the compiler didn't run and the inputs/outputs didn't change.cc @smasher164