Skip to content

Conversation

@jakepetroules
Copy link
Contributor

This resolves an issue where outputs of build tool plugins could be emitted to a random output directory based on whatever the working directory of the calling process happened to be at the time the build tool plugin was executed.

Closes #7930

…ally This resolves an issue where outputs of build tool plugins could be emitted to a random output directory based on whatever the working directory of the calling process happened to be at the time the build tool plugin was executed. Closes #7930
@jakepetroules
Copy link
Contributor Author

@swift-ci test

@dschaefer2
Copy link
Member

dschaefer2 commented May 9, 2025

Thanks! Better to be explicit for sure. Still curious what scenario caused this. It would have to have been a sub directory of the package since --package-path actually does a chdir to that dir.

@jakepetroules jakepetroules changed the title Set the working directory of build tool plugin commands deterministically [BLOCKED] Set the working directory of build tool plugin commands deterministically May 9, 2025
@jakepetroules
Copy link
Contributor Author

Actually, I'm not convinced this will fully solve the problem; the compile commands created from the build tool plugin outputs ultimately need to have their working directory set too.

Additionally, this will require using the llbuild working-directory attribute, so we can't land it now because of swiftlang/swift-llbuild#980. So moving to draft for now...

@jakepetroules jakepetroules marked this pull request as draft May 9, 2025 04:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants