Workaround for build failure in cdacreader when EmitCompilerGeneratedFiles=true
#101279
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we build
cdacreader, we run theLinkNativetarget. This depends onCompilenotBuild, which means theBuildOnlySettingstarget that setsBuildingProject=truedoesn't run. WhenEmitCompilerGeneratedFiles=true, this results in the generated output path not being created and the compiler erroring when trying to emit files to the path. See dotnet/roslyn#73075.CodeQL injects
-p:EmitCompilerGeneratedFiles=trueinto the command line arguments. This was resulting in build failures in jobs where CodeQL is run.This change adds a workaround to our infrastructure for building NativeAOT-ed runtime components such that the generated output path is always created if
EmitCompilerGeneratedFiles=true. Manually tested by explicitly passing that property on the command line.Fixes dotnet/source-build#4335