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
Statically linking coreclr and clrjit in single file host #43556
Statically linking coreclr and clrjit in single file host #43556
Changes from all commits
7872a2b
4fac39a
038d2af
c34ca9b
7a4dc8f
250d3fc
c4f8e6c
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.
I keep wondering if we should unify the configuration of runtime and installer instead (so that we can never build different flavors of those two). I am not happy about hacking around defines and options to make things build and also about the fact that we now compile the host sources twice.
@vitek-karas do you see a benefit in being able to build the runtime with debug coreclr and release installer or vice versa?
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 do not think we need a general solution here. This will not be needed after we move hosts to clr partition (tracked by #43700).
We just need to finish superhost - i.e. enable it not only on Linux.
Then we should move the entire thing together with tests and required infra to clr partition where it will not be possible to have different configs for the native parts.
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.
As for mixed configurations - I think at least combinations with Checked runtime are useful, for the same reason they are useful with libs - running installer tests with Debug runtime is very slow.