Closed optimality closed 1 year ago
Hey, Austin! Thanks for giving these rules a whirl and reporting the issue. Love the username :)
I use (and help maintain) both together, so 🤦🏻 I hadn't tested this case.
I just pushed up a fix--you'll need to add another short snippet to your WORKSPACE. (Unfortunately, this just isn't something current Bazel handles very well--pre bzlmod. More details in the commit backlinked above.)
Cheers! Chris
P.S. Thanks for your willingness to file a PR if/when you see your way to a fix. This one's a weird, tricky bazel edge case, but I'm hoping we'll get to collaborate more in the future.
Thanks for the fix, much appreciated! Big fan of this and your compile commands extractor.
:) My pleasure, man. Thanks for reporting--and replying back.
If you're down to share, I'd love to know what you're building with them! Helps me understand use cases and feel good about building the tools.
Checking back in: Working for you ok @optimality?
One place I'd love your help: Compile commands extractor kinda exploded on its own (in a good way) but this one's been slower on the uptake. Any other ways you can think of to make it more valuable to more people--or other things that'd have helped you find it? (Unblocking usage without boost is huge--I'm wondering if there are other ways I'm accidentally cutting off usage.)
When I added the suggested code to my WORKSPACE file and attempted to build, I received the following error:
I was able to resolve this by copying your
http_archive
definition ofcom_github_nelhage_rules_boost
fromworkspace_setup.bzl
and putting it before thehedron_make_cc_https_easy
invocation in my WORKSPACE file, so that my WORKSPACE looks like this:I believe you can replicate this easily in an empty project.
I think the underlying issue is that in
workspace_setup.bzl
on line 3 you havebut
rules_boost
hasn't been imported yet; that happens on line 31.Not sure what a good fix would be or I would've just sent a PR, sorry.