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

.o files appear in the current directory #187

Open
laurentlb opened this issue May 6, 2024 · 1 comment
Open

.o files appear in the current directory #187

laurentlb opened this issue May 6, 2024 · 1 comment

Comments

@laurentlb
Copy link

I've just tried this tool and it works well. Thanks a lot for your work!

However, when I run the command bazel run @hedron_compile_commands//:refresh_all, it adds lots of .o files in the current (workspace root) directory, as well as the compile_commands.json file. Is it a know issue? Am I doing something wrong?

MODULE.bazel:

bazel_dep(name = "hedron_compile_commands", dev_dependency = True)
git_override(
    module_name = "hedron_compile_commands",
    remote = "https://github.com/hedronvision/bazel-compile-commands-extractor.git",
    commit = "a14ad3a64e7bf398ab48105aaa0348e032ac87f8",
)
@cpsauer
Copy link
Contributor

cpsauer commented May 23, 2024

Hi Laurent! Great to meet you--and honored you used this tool and by your kind words. Sorry to be slow in replying; got way backed up here.

Showing you with .o's is definitely not a known issue or desirable behavior. Thanks for reporting. Any idea what might be causing? Does it happen just running this tool on itself? (I'm trying to repro, but failing, sadly. Does sound like it could be a flag interaction issue with the header-finding code, maybe.)

Thanks again--and happy coding,
Chris

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

2 participants