Make the build configuration under Bazel more correct. #1600
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JSON_USE_EXCEPTIONandJSON_HAS_INT64as Bazel config flags with defaults that match the existing Bazel build. (These may not match the non Bazel build defaults but that is a pre-existing divergence and Bazel by default does mostly static builds so the issues about dynamic API issues don't exist unless someone intentionally steps off the normal path.)//:jsoncppfrom usingcoptstodefinesforJSON_USE_EXCEPTIONandJSON_HAS_INT64so that rules that depend on it get the same config.src/test_lib_json/fuzz.cpprespectJSON_USE_EXCEPTION.#ifdefstuff that should only be used withJSON_USE_EXCEPTION.Note:
See also #1601
Testing:
This builds with all 4 combinations: