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
Write link file list as a build command #6606
Conversation
c72ae46
to
d2fc83f
Compare
Updated some tests that were relying on the file existing after build planning to instead look at the build plan itself. |
@swift-ci please smoke test |
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 is great!
Failure is
this is one of the tests I updated and it does seem to have cases for different platforms, so makes sense that it is failing. |
d2fc83f
to
734e28d
Compare
@swift-ci please smoke test |
734e28d
to
ad99ee5
Compare
There was a small typo in the test change. |
@swift-ci please smoke test |
ad99ee5
to
9e01372
Compare
@swift-ci please smoke test |
@swift-ci please smoke test windows |
1 similar comment
@swift-ci please smoke test windows |
Hm, seems like Windows job isn't starting again... |
This should be ready for review now, but I do want to make sure we can also support implementing |
@swift-ci please smoke test windows |
Windows failure is infra related. |
Got output file maps working with the same infrastructure, so I think this should be good. |
b222551
to
88b203a
Compare
Oh interesting, looks like running |
We actually can't format the code in |
88b203a
to
c90da05
Compare
@swift-ci please smoke test |
@swift-ci please smoke test windows |
This moves the generation of link file lists into the build system instead of doing it ad-hoc outside of the build. For this, we have a new `WriteAuxiliaryFile` tool and associated command that should be usable for any kind of writing of auxiliary files during the build. Note that this change opted to not touch the existing infrastructure for in-process tools, so any inputs that are needed for the file generation will need to be flattened into a generic array of input nodes. The different types of file generation are keyed off a virtual node at the start of that array.
c90da05
to
9534ca1
Compare
@swift-ci please smoke test |
@swift-ci please smoke test windows |
1 similar comment
@swift-ci please smoke test windows |
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.
nice work
@swift-ci please smoke test windows |
Windows failure is apple/swift#66138 |
Please test with following PRs: @swift-ci please test windows platform |
Would we be able to merge this into release/5.9. It fixes a major issue where sourcekit-lsp breaks build plugins |
It has been in |
sgtm |
Hm, straight cherry-pick is not working, I am seeing a few test failures being introduced. So this won't be trivial to include in 5.9. |
Opened a PR for the cherry-pick here but it needs investigation into the test issues that this causes. |
This moves the generation of link file lists into the build system instead of doing it ad-hoc outside of the build. For this, we have a new
WriteAuxiliaryFile
tool and associated command that should be usable for any kind of writing of auxiliary files during the build.Note that this change opted to not touch the existing infrastructure for in-process tools, so any inputs that are needed for the file generation will need to be flattened into a generic array of input nodes. The different types of file generation are keyed off a virtual node at the start of that array.