-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Linux] Enable build-ids. #4995
[Linux] Enable build-ids. #4995
Conversation
We should use build IDs on Linux so that we can identify the built artefacts, and also so that we can match them up with debug information should we choose to separate it. rdar://130582768
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.
Overall the change looks good to me!
Since we don't have CI setup on this branch yet, I used my other WIP PRs to kick off this linux test which includes this PR: https://ci.swift.org/job/swift-PR-Linux/16070/. Let's wait for that to pass before merging (Linux is in the state where swift-ci testing should pass).
Do we also need to do the same for all of the dependencies (swift-foundation, swift-foundation-icu, and swift-collections)?
👍 Yes, ideally, anything that is installed as a |
I'm seeing some build failures that appear to be new with this change:
This symbol should be exported from
Is it possible that this change introduced that issue? |
Oh I apologize, that was due to an issue on my end. New test run kicked off at https://ci.swift.org/job/swift-PR-Linux/16085/ |
Ok the new linux test passed so this looks good to me, thanks! |
This reverts commit f186ff8. This is incorrectly being applied to Windows builds as well.
We should use build IDs on Linux so that we can identify the built artefacts, and also so that we can match them up with debug information should we choose to separate it.
rdar://130582768