Change C include statements to use " instead of <#16
Conversation
|
Probably fine, though a little confused about what Bazel is doing here. Can you see if you can get CI working here again? I'll feel a little better with a green build. Feel free to just ditch the "ubuntu-old" job. |
It's specifically for getting CXX to work with Bazel. I haven't totally tracked it down, but I think it's Bazel's
For sure! It looks like it has something to do with trying to find SIMD instructions for |
f72030c to
8777fb0
Compare
Ah, well, that would explain it... |
9adc73b to
b3b5459
Compare
|
For the build issue, it looks like clang got rig of the Adding Side stepping all of this, the |
benesch
left a comment
There was a problem hiding this comment.
Great, let's roll with this. Thanks for fixing this up, Parker!
This PR upgrades our `protobuf-native` dependency ### Motivation Pull in MaterializeInc/rust-protobuf-native#16 for Bazel ### Checklist - [ ] This PR has adequate test coverage / QA involvement has been duly considered. ([trigger-ci for additional test/nightly runs](https://trigger-ci.dev.materialize.com/)) - [ ] This PR has an associated up-to-date [design doc](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/README.md), is a design doc ([template](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/design/00000000_template.md)), or is sufficiently small to not require a design. <!-- Reference the design in the description. --> - [ ] If this PR evolves [an existing `$T ⇔ Proto$T` mapping](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/command-and-response-binary-encoding.md) (possibly in a backwards-incompatible way), then it is tagged with a `T-proto` label. - [ ] If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label ([example](https://github.com/MaterializeInc/cloud/pull/5021)). <!-- Ask in #team-cloud on Slack if you need help preparing the cloud PR. --> - [x] This PR includes the following [user-facing behavior changes](https://github.com/MaterializeInc/materialize/blob/main/doc/developer/guide-changes.md#what-changes-require-a-release-note): - N/a
AFAIU using angle brackets for
#includestatements is generally used for system headers while double-quotes prioritizes headers in the current working directory (stackoverflow). It's compiler dependent, but using double-quotes fixes some issues I ran into while building with clang via Bazel