-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix static-lib AOT Mono builds #103988
Fix static-lib AOT Mono builds #103988
Conversation
@kotlarmilos what pipeline should I run to ensure I'm getting good coverage here? |
/azp run runtime-ioslike |
Azure Pipelines successfully started running 1 pipeline(s). |
|
Looks like it's working. I'll mark this ready for review. |
/azp run runtime-ioslikesimulator |
Azure Pipelines successfully started running 1 pipeline(s). |
@jkoritzinsky Please take a look at simulator failures as they seem related: https://dev.azure.com/dnceng-public/public/_build/results?buildId=721222&view=logs&j=07effcfd-c63d-5008-e811-03b29530f5cb&t=1b65cd35-7643-520a-edf8-09ec895c1ca1 |
@@ -231,7 +231,9 @@ if (ENABLE_PERFTRACING AND "${MONO_DIAGNOSTICS_TRACING_COMPONENT_NAME}" IN_LIST | |||
list(APPEND mono-components-objects $<TARGET_OBJECTS:eventpipe-mono-objects> $<TARGET_OBJECTS:dn-containers>) | |||
endif() | |||
if (TARGET mono-component-${MONO_DIAGNOSTICS_TRACING_COMPONENT_NAME}-static) | |||
target_sources(mono-component-${MONO_DIAGNOSTICS_TRACING_COMPONENT_NAME}-static PRIVATE $<TARGET_OBJECTS:eventpipe-mono-objects> $<TARGET_OBJECTS:dn-containers>) | |||
# We don't add dn-containers here as any scenario that uses this target will also use the monosgen-static target, |
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.
@akoeplinger do you recall if that's true even for simulator?
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 so, yes
This fix resolves the device failure caused by symbol duplication. However, simulators are still encountering a different issue. Looking at logs between device and simulator, I noticed the following difference: Lines 72 to 75 in 9906682
Line 682 in 9906682
@akoeplinger Could we align these params for the device and simulator? |
The simulator failures are only when building the I'm doing my best to investigate, but I don't have a Mac available today. |
…g is being linked in
/azp run runtime-ioslike, runtime-ioslikesimulator |
Azure Pipelines successfully started running 2 pipeline(s). |
/ba-g Failure is an AzDO infra issue |
Fixes #103982