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
Currently the tool generates an /external symlink. It'd be nice to be able to customize the name, and for example by default prefix it with bazel- similar to other bazel-* symlinks.
The text was updated successfully, but these errors were encountered:
Hey Chandler! Thanks for giving the tool a go--and for writing in.
Somewhat common request, but much harder to do than you might think, unfortunately. The external symlink's name is matching the one in Bazel's internal compilation environment (along with bazel-out, but they don't have a prefix for external). So changing the symlink name would require significant additional complexity in this tool, manually patching all possible flag variants for all toolchains (rather than (mostly) exporting the flags from Bazel as they actually are). Doable, probably, but I think not worth it. Could ask bazel if they'd change it? Willing also to take a PR, but it's gonna be tricky to get all the cases. (See past efforts.)
Saw your backlinked PR, btw. Definitely don't check in //external; the format varies on Windows. No need to add it or compile_commands.json to .gitignore if you don't want to; we automatically add to the hidden gitignore in .git/info/exclude. See _ensure_gitignore_entries_exist if you're curious.
Currently the tool generates an
/external
symlink. It'd be nice to be able to customize the name, and for example by default prefix it withbazel-
similar to otherbazel-*
symlinks.The text was updated successfully, but these errors were encountered: