-
Notifications
You must be signed in to change notification settings - Fork 324
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
feat: nlohmann_json add single_include package #2865
Conversation
Hello @keith, modules you maintain (nlohmann_json) have been updated in this PR. Please review the changes. |
25ff0a3
to
106bfb5
Compare
I'd put it in the toplevel BUILD file. Keep the original Reasoning: for projects that also support the 'old' WORKSPACE file, they have a simple way to provide a toplevel BUILD file, but not a nested structure. A project that needs to compile with before and after bzlmod should be able to do that easily. Example of such a project and how it will be working nicely with a toplevel target : chipsalliance/verible#2268 |
7b71bd4
to
a26590b
Compare
LGTM |
I guess @keith needs to add a review ? |
modules/nlohmann_json/3.11.3.bcr.1/patches/add_singleheader_target.patch
Outdated
Show resolved
Hide resolved
i think we should avoid |
a26590b
to
55de76b
Compare
Require module maintainers' approval for newly pushed changes.
We used to patch the module to allow the single header version of the library to be available. Not needed anymore thanks to @lromor who added it in BCR in bazelbuild/bazel-central-registry#2865 Now, use the same name for the old-WORKSPACE based build and the new MODULE based build.
We used to patch the module to allow the single header version of the library to be available. Not needed anymore thanks to @lromor who added it in BCR in bazelbuild/bazel-central-registry#2865 Now, use the same name for the old-WORKSPACE based build and the new MODULE based build. While at it: fix formatting in MODULE.bazel.
We used to patch the module to allow the single header version of the library to be available. Not needed anymore thanks to @lromor who added it in BCR in bazelbuild/bazel-central-registry#2865 Now, use the same name for the old-WORKSPACE based build and the new MODULE based build; for that the name we provide in bazel/jsonhpp.BUILD, and all uses in the repo, had to be changed. While at it: fix formatting in MODULE.bazel.
We used to patch the module to allow the single header version of the library to be available. Not needed anymore thanks to @lromor who added it in BCR in bazelbuild/bazel-central-registry#2865 Now, use the same name for the old-WORKSPACE based build and the new MODULE based build; for that the name we provide in bazel/jsonhpp.BUILD, and all uses in the repo, had to be changed. While at it: fix formatting in MODULE.bazel.
We used to patch the module to allow the single header version of the library to be available. Not needed anymore thanks to @lromor who added it in BCR in bazelbuild/bazel-central-registry#2865 Now, use the same name for the old-WORKSPACE based build and the new MODULE based build; for that the name we provide in bazel/jsonhpp.BUILD, and all uses in the repo, had to be changed. While at it: fix formatting in MODULE.bazel.
nlohmann_json provides a new single-header target. Add it as optional target to the the bazel module. --------- Co-authored-by: Keith Smiley <[email protected]>
nlohmann_json provides a new single-header target. Add it as optional target to the the bazel module.