-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Clean up AOT publish process #73416
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean up AOT publish process #73416
Changes from 27 commits
b9d18e1
62a302a
b5f37f0
3b86b66
e992c9b
dcf710c
da529fd
3cb58e6
5696f2d
941d558
363fd28
48b0f74
c1fb84e
eb13dc8
294c463
2a07fcc
8038c58
45c21cb
7867291
5907416
b12795b
80cedc4
a52fcdd
80faf94
141c61f
de74e2b
3d48f00
62ce9bd
ff574f8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,10 +10,11 @@ Copyright (c) .NET Foundation. All rights reserved. | |
| *********************************************************************************************** | ||
| --> | ||
| <Project> | ||
|
|
||
| <PropertyGroup> | ||
| <!-- Set the publishAot property to true if not set--> | ||
| <PublishAot Condition="'$(PublishAot)' == ''">true</PublishAot> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I understand it correctly, this was needed because we do the ".targets included from a .props file" antipattern - I think we discussed this in one of the past pull request - to do the real fix, we likely need to break up Microsoft.DotNet.ILCompiler.targets into Microsoft.DotNet.ILCompiler.targets and Microsoft.DotNet.ILCompiler.props as needed. (The convention is that .props are included before the user project, .targets get included after the user provided stuff - we would see PublishAot being set there if the user wants it.)
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Most of the stuff that is already in .targets should be in .targets. We wouldn't probably have much (if anything?) in the props.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think it's because we are importing targets from props (if we are, that should probably be fixed) - this was needed to preserve the OOB package behavior where the packagereference was all that was needed to turn on AOT publish (you didn't need to set PublishAot explicitly).
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, you're right. I saw .targets in a .props and I thought it's an |
||
| <!-- N.B. The ILCompilerTargetsPath is used as a sentinel to indicate a version of this file has already been imported. It will also be the path | ||
| used to import the targets later in the SDK. --> | ||
| <ILCompilerTargetsPath>$(MSBuildThisFileDirectory)Microsoft.DotNet.ILCompiler.targets</ILCompilerTargetsPath> | ||
| <ILCompilerTargetsPath>$(MSBuildThisFileDirectory)Microsoft.DotNet.ILCompiler.SingleEntry.targets</ILCompilerTargetsPath> | ||
| </PropertyGroup> | ||
| </Project> | ||
Uh oh!
There was an error while loading. Please reload this page.