You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 theFoo.pcm
using-fmodule-file=Foo.pcm
, it will fail to build.Am I right?
The text was updated successfully, but these errors were encountered: