Replies: 1 comment
-
|
Bumping this thread up for more eyes from the community. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Continuing the discussion from #28321 and tagging OP @ShubhamIIITD
I saw a similar thread on a forum where the Windows filesystem faced some unexpected failures when a file was rapidly renamed on a shared filesystem: https://knowledge.broadcom.com/external/article/129971/xcomn0508e-error-replacing-or-creating-f.html
I then tried to ensure that Bazel does not leave any residues at my network drive M:\ by making the following changes to the
.bazelrcfile:The above should've ideally kept temporary files created by operations executed through Bazel on my local drive C:\ but even with this change, I am not able to progress on the Bazel build for a sample stored on my network location.
I got some suggestions from @tjgq regarding further steps for identifying the issues when building my code stored on a network location (say mapped network drive M:) while my Bazel installation lies on my local machine (C:).
Before trying them out, I wanted to ask the community if there is actually a way to get Bazel builds running on Windows when your installation is local but the code base lies on a network location? I got my setup working perfectly fine on Debian 12.10 and I feel that I have something fundamental amiss for Windows 11, could anyone point me to any relevant documentation/blogs?
Beta Was this translation helpful? Give feedback.
All reactions