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.
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
Creating a runtime pack artifacts directory in the libraries build #34662
Creating a runtime pack artifacts directory in the libraries build #34662
Changes from 8 commits
8321dea
be068f2
d22cee8
e432bbc
002b96b
c3ba797
4d91c78
94a03ab
3cafc0f
d71ddd1
84241b1
b5568e4
07965e5
2b3b736
484d0ff
05d4759
73b6800
0dad68b
d465796
60b9009
23da306
211eece
2d4d7f4
757c871
bc3991a
ba6d021
0d46895
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
It seems like we're starting to use these long condition in a lot of places:
'$(TargetOS)' == 'iOS' or '$(TargetOS)' == 'tvOS' or '$(TargetOS)' == 'Android'
-- should we introduce a property to make it easier? Something likeTargetsMobile
?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 was wondering the same thing.
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 think it would make sense to do it now before we start adding it to more places. Looks like we should be able to define it here https://github.com/dotnet/runtime/blob/07965e57e294493757bb14f274137d7047628d3b/src/libraries/targetframework.props in the according
when
statements.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.
Do we want to replace all instances of
'$(TargetOS)' == 'iOS' or ...
with aTargetsMobile
property? Defining it intargetframework.props
and replacing all instances of that condition everywhere seems to break things. Replacing only insrc/installer
andsrc/libraries
builds w/o error, but we then lose a couple folderslib-runtime-packs/data
lib-runtime-packs/runtimes/$(PackageRID)/native
.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 can do it in a separate PR to not complicate things here.
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.
Share values with installer project tree? (Move to common ancestor?)
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.
Where would be a good place to place these properties in
<runtimeroot>/src/Directory.Build.props
?Is it a significant impact to performance/organization to move it up? I'm not familiar enough to know now if those properties have a chance of changing or differing between the directories in
<runtimeroot>/src
. If they were to differ later would it be better to have each specify their own properties?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.
It might not be worth it. My knee-jerk reaction is that duplicating code is what needs justification rather than reusing it, so just a quick suggestion.
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.
Let's open an issue for this. Consolidate all places in props and targets where we use Microsoft.NETCore.App to a single shared property.
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.
Given this target is specific to
Mono
should we includeMono
in the target name?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.
there are going to be some differences with desktop mono, so I'd like to address them in a separate PR.
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.
Do you have an issue tracking this work we can reference here?
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.
#34203