-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[MonoAOTCompiler] more properties & custom WorkingDirectory #62725
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
Merged
jonathanpeppers
merged 1 commit into
dotnet:main
from
jonathanpeppers:monoaotcompiler-android-fixes
Dec 15, 2021
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it might be better to have a
ITaskItem? CommonAotArgumentswith metadata which act as the key-value pairs to pass to--aot.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LdFlagswill contain a;on Android. So it seems like using item metadata would always have an issue?Our usage is now:
But maybe
$(AndroidAotAdditionalArguments)could be passed in a different way? What would the XML look like forITaskItem? CommonAotArguments?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We won't split the metadata on
CommonAotArguments.As for the metadata names, we could either use the real argument name, like
<ld-flags>foo; bar</ld-flags>, or we could have<LdFlags>foo; bar</LdFlags>and convert to the real name in the task.or
And you could have a
<PassVerbatim>..</PassVerbatim>metadata (or better name) for just any additional string to be passed to--aot.Feel free to push back, I'm just thinking aloud.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The weird part about using
@(CommonAotArguments), is that you putInclude=""with any random word inside. You can't leave outInclude, or that would be an empty item group. I also like the idea of having C# properties, as it checks for typos -- you'll get an MSBuild error if you putLdlFlagsinstead ofLdFlags.Adding something like
@(CommonAotArguments)might be ok if there is some unknown set. At least for Android, these changes now include every parameter we use. Are there many more not represented here?