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

Cannot build with bazel #25

Closed
vks opened this issue Oct 15, 2016 · 6 comments
Closed

Cannot build with bazel #25

vks opened this issue Oct 15, 2016 · 6 comments

Comments

@vks
Copy link
Contributor

vks commented Oct 15, 2016

I'm getting this error when trying to compile highwayhash with bazel:

ERROR: highwayhash/BUILD:39:1: no such package 'base': BUILD file not found on package path and referenced by '//:vector_test'.

Maybe base is something internal at Google?

@jan-wassenberg
Copy link
Member

Hi Vinzent, that's correct, the real problem is the lack of "manual" tag. I've added it, so that test target should no longer be built unless manually specified. Thanks for reporting, and please let me know if that doesn't solve it for you :)

@vks
Copy link
Contributor Author

vks commented Oct 19, 2016

Thanks for the fix, now I'm getting this error:

ERROR: highwayhash/BUILD:131:16: in includes attribute of cc_library rule //:data_parallel: '.' resolves to the workspace root, which would allow this rule and all of its transitive dependents to include any file in your workspace. Please include only what you need.

@jan-wassenberg
Copy link
Member

Thanks for bringing this up. Looks like Bazel has changed its behavior, this was previously allowed.
Coincidentally we're changing the file structure to speed up builds, which will also remove the problem Bazel complains about.

Some questions for you: would it be troublesome if we changed the paths to #include third_party/highwayhash/..."?
Also, do you need the Bazel build capability, or is the Makefile sufficient?

I'm trying to keep the github/internal versions in sync without conversions in either direction, but it is getting a bit difficult :)

@vks
Copy link
Contributor Author

vks commented Oct 23, 2016

About your questions:

  • I don't think changing the includes would be a problem.
  • I'm linking statically against bazel, if I understand correctly this is currently not supported by the makefile. In fact, I would prefer to use make for the Rust bindings, because it is a much more lightweight/common dependency. So for me it would be fine to only have the makefile, if it supported static linking.

Maybe the best path forward is to use the Bazel file only internally at Google and maintain only the Makefile for the public version of highwayhash?

@vks
Copy link
Contributor Author

vks commented Oct 23, 2016

With #26 I no longer need Bazel for the Rust bindings.

@jan-wassenberg
Copy link
Member

Thank you for the Makefile update :) The include path changes and a few other fixes are coming soon.

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