Mono runtime component infrastructure including EventPipe/DiagnosticsServer as a Mono runtime component. #50837
Conversation
lateralusX
changed the title
|
Tagging subscribers to this area: @directhex Issue DetailsImplementation of Mono component infrastructure initial worked on in draft PR, #49913. This PR replace that work but documentation (https://github.com/dotnet/runtime/blob/af8e756e2dd6a858066a8de61d569a4abe749284/docs/design/mono/components.md) is still left in that PR and will probably be moved to separate PR. This PR also includes a port of Mono EventPipe/DiagnosticsServer library over to new component infrastructure. Before all packaging/deploy have been fixed for platforms that will switch over to hosting components as shared libraries, all components will be build and linked using the static linkage scenario outline in document above. Once package and deploy is resolved for dynamic linking scenarios, we will switch this for corresponding platforms in separate PR. @lambdageek @akoeplinger @steveisok
|
lateralusX
changed the title
lateralusX
force-pushed
the
lateralusX/eventpipe-as-component
branch
from
be59f74 to
4d7078c
Compare
lateralusX
changed the title
lateralusX
requested review from
CoffeeFlux,
lambdageek,
marek-safar,
SamMonoRT,
thaystg and
vargaz
as code owners
lateralusX
force-pushed
the
lateralusX/eventpipe-as-component
branch
from
42f99dd to
277159c
Compare
|
Rebased on main to resolve build/test error in CoreClr on Linux. |
ghost
locked as resolved and limited conversation to collaborators
Implementation of Mono runtime component infrastructure initial worked on in draft PR, #49913. This PR replace that work but documentation (https://github.com/dotnet/runtime/blob/af8e756e2dd6a858066a8de61d569a4abe749284/docs/design/mono/components.md) is still left in that PR and will probably be moved to separate PR and merged.
This PR also includes a port of Mono EventPipe/DiagnosticsServer library over to new runtime component infrastructure.
Before all packaging/deploy have been fixed for platforms that will switch over to hosting components as shared libraries, all components will be build and linked using the static linkage scenario outline in document above. Once package and deploy is resolved for dynamic linking scenarios, we will switch this for corresponding platforms in separate PR.
@lambdageek @akoeplinger @steveisok