Skip to content
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

swift_c_module and remote cache #1296

Open
PhilCai1993 opened this issue Aug 8, 2024 · 0 comments
Open

swift_c_module and remote cache #1296

PhilCai1993 opened this issue Aug 8, 2024 · 0 comments

Comments

@PhilCai1993
Copy link

PhilCai1993 commented Aug 8, 2024

I'm a little curious, when using swift_c_module, the .pcm files emitted by swiftc would store some absolute paths, like the path of the modulemap, or the path of Xcode SDK, etc.

When we are attempting to use bazel remote cache, the pcm files will be shared accross different machines, if possible.

But the absolute paths might break the build.

For example, Mac_1 produces Foo.pcm, and there might be some absolute paths inside it, like /Users/**Mac_1**/Xcode.app/.....
If another Mac_2 gets the Foo.pcm using remote cache(Since the inputs are the same), and loads the Foo.pcm using -fmodule-file=Foo.pcm, it will fail to build.

Am I right?

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

No branches or pull requests

1 participant