Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork84
Bazel: Define a minimal Bazel module#269
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This defines the very minimal integration with Bazel build system.The definitions follow the spirit of README.md in that the build rulespackage the library such that it can be included with```c```
| compatibility_level = 1, | ||
| ) | ||
| bazel_dep(name = "zlib", version = "1.3.1") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I'm not familiar with bazel, does this specify 1.3.1 and only 1.3.1 or the minimum version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Iflibspng is the only user ofzlib in a bazel workspace, then it would mean 1.3.1 exactly.
If there is anotherbazel_dep with, say,zlib 1.3.2 in its dependencies, then
- if 1.3.1 and 1.3.2 have the same
compatibility_levelin their definition (here:https://github.com/bazelbuild/bazel-central-registry/blob/main/modules/zlib/1.3.1/MODULE.bazel#L4 ), the later 1.3.2 version is pulled; - otherwise, the dependency graph cannot be resolved.
Full details:
This defines the very minimal integration with Bazel build system. The definitions follow the spirit of README.md in that the build rules package the library such that it can be included with