-
Notifications
You must be signed in to change notification settings - Fork 65
[WIP] Add publishing step #208
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
Conversation
8c85f9a to
9555d85
Compare
|
@dotnet/jit-contrib PTAL |
|
I am not sure whether we need to publish for each arch/os configuration or it would be good enough to publish binaries built targeting any RID |
|
If you're only building managed code, I think the easiest thing to do is to publish framework-dependent, without passing a RID. That should be usable on any platform (as long as you already have a framework on the target machine - if I understand your scenario, it sounds like you'll be placing the built binaries into CORE_ROOT, which should work AFAIK). Just note that by default "dotnet publish" will still produce an apphost for the host platform - you just wouldn't use that. |
BruceForstall
left a comment
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 don't have much experience understanding this format, but it seems ok to me.
|
Not going to work on this in near future. |
No description provided.