Skip to content

Conversation

@mhegazy
Copy link
Collaborator

@mhegazy mhegazy commented Oct 20, 2025

We were not building or packaging compiler-rt. this brings the changes in build.ps1 over to CI.

Here is a downstream run:https://github.com/thebrowsercompany/swift-build/actions/runs/18619136557

run: |
$litOutput = python ${{ github.workspace }}/SourceCache/llvm-project/llvm/utils/lit/lit.py --version
$litVersion = ($litOutput | Select-String -Pattern 'lit (\d+)' | ForEach-Object { $_.Matches[0].Groups[1].Value })
echo "llvm-version=$litVersion" >> $env:GITHUB_OUTPUT
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't entirely guaranteed to be correct. lit is available as a separate pip project as well.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure i understand what you mean?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly that I'm not sure if we should be using lit as the source of the version information.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@compnerd should we have this as an input to the build? or is there a better way to get the version?

@mhegazy mhegazy force-pushed the upstream-compiler-rt branch from 034e8b3 to 33d3228 Compare October 21, 2025 00:55
@mhegazy mhegazy requested a review from compnerd October 21, 2025 00:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants