Closed andrewkatson closed 4 weeks ago
Okay I have figured it out. Configure
looks for a specific path to a file named MODULES.txt
not a directory generally speaking. And bazel
moves that file when included in the data
of whatever rule you use. So the solution is to modify Configure
to look at the right path.
I posted a stack overflow: https://stackoverflow.com/questions/78713054/parameter-to-use-fallback-must-be-a-directory-not-a-file about this issue. Is it simply that MacOS doesn't support compilation because I tried
sh_binary
that runs a perl script and I get the same error. I am wondering if there is something with bazel sandboxing that is causing this because a shell script works and running the perl script works outside of bazel.