-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[Performance] Add static linking build for CoreCLR Android #116093
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
[Performance] Add static linking build for CoreCLR Android #116093
Conversation
Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger |
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.
Pull Request Overview
This PR introduces a new static linking build configuration for the CoreCLR JIT on Android to help track on-disk size. Key changes include:
- Adding a new build step to run a static linking build for the Android sample app.
- Publishing and archiving the resulting build logs and artifacts.
- Cleaning up the bindir after processing the artifacts.
Comments suppressed due to low confidence (1)
eng/pipelines/performance/templates/build-perf-sample-apps.yml:100
- Ensure that this cleanup command targets only directories dedicated to build outputs to avoid accidental deletion if the Build.SourcesDirectory variable is misconfigured.
- script: rm -r -f $(Build.SourcesDirectory)/artifacts/bin/AndroidSampleApp
@@ -78,6 +78,29 @@ steps: | |||
workingDirectory: $(Build.SourcesDirectory)/artifacts/bin | |||
displayName: clean bindir | |||
|
|||
# CoreCLR JIT static linking build | |||
- script: make run TARGET_ARCH=arm64 DEPLOY_AND_RUN=false RUNTIME_FLAVOR=CoreCLR STATIC_LINKING=true |
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.
[nitpick] Consider externalizing build configuration options (such as TARGET_ARCH, RUNTIME_FLAVOR, and STATIC_LINKING) into variables or a template to improve reusability and clarity for similar build steps.
- script: make run TARGET_ARCH=arm64 DEPLOY_AND_RUN=false RUNTIME_FLAVOR=CoreCLR STATIC_LINKING=true | |
- script: make run TARGET_ARCH=${{ parameters.targetArch }} DEPLOY_AND_RUN=${{ parameters.deployAndRun }} RUNTIME_FLAVOR=${{ parameters.runtimeFlavor }} STATIC_LINKING=${{ parameters.staticLinking }} |
Copilot uses AI. Check for mistakes.
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.
This looks good to me.
Description
This PR adds a static linking build configuration for the CoreCLR JIT on Android, to track its on-disk size.