protobuf/ci/macOS.bazelrc

import common.bazelrc

build --cxxopt=-std=c++17 --host_cxxopt=-std=c++17
build --cxxopt="-Woverloaded-virtual"
build --copt="-Werror" --copt="-Wno-sign-compare" --copt="-Wno-sign-conversion" --copt="-Wno-error=sign-conversion" --copt="-Wno-deprecated-declarations"
common --repo_env=BAZEL_NO_APPLE_CPP_TOOLCHAIN=1
common --xcode_version_config=@com_google_protobuf//.github:host_xcodes
Migrate non-Linux C++ tests to GHA actions PiperOrigin-RevId: 506683178 2 years ago			`import common.bazelrc`

Bump minimum C++ version to C++17 after branch cut for v29. Branch cut for v29 is done on 2024-09-30: https://github.com/protocolbuffers/protobuf/releases/tag/v29.0-rc1 The next version v30 will be a breaking release. The release date is scheduled after the EOL of C++14 support on 2024-12-15 for Google open source projects generally: https://github.com/google/oss-policies-info/blob/main/foundational-cxx-support-matrix.md This commit allows us to start taking advantage of C++17 features now. Some issues I ran into while upgrading: Two GCC 9.5 bugs related to -Wunused-but-set-parameter: - https://godbolt.org/z/qo51cKe7b - https://godbolt.org/z/65qW3vGhP Another GCC warning related to -Wself-assign in a template. There is a custom ASAN check that is not yet open sourced. I'll see if I can open source them in a subsequent commit. #test-continuous PiperOrigin-RevId: 687435042 2 months ago			`build --cxxopt=-std=c++17 --host_cxxopt=-std=c++17`
Reduce our reliance on COPTS variable for compiler flags It's somewhat tedious to explicitly set this option on all of our C++ targets, so I think ideally we should rely primarily on bazelrc files for setting compiler flags. I tried to completely remove `COPTS`, but unfortunately that did not work out--we have so many `-Wsign-compare` warnings that I think we need to keep suppressing them for now or else we will get a lot of complaints. However, I was able to get to the point where `-Wno-sign-compare` is the only flag we need in `COPTS` for non-Windows builds. I explicitly set `-DHAVE_ZLIB` on just the two targets that need it, and removed `-Wno-nonnull` since we are already compliant with that warning. I moved `-Woverloaded-virtual` to our bazelrc files so that CI will enforce that we remain compliant with that. PiperOrigin-RevId: 684863987 2 months ago			`build --cxxopt="-Woverloaded-virtual"`
Add `[[deprecated]]` attribute when generating enums and classes. When the user adds `option deprecated = true` for an `enum` or `message`, we should add the `[[deprecated]]` attribute to the generated C++ `enum` or `class`. PiperOrigin-RevId: 670583253 3 months ago			`build --copt="-Werror" --copt="-Wno-sign-compare" --copt="-Wno-sign-conversion" --copt="-Wno-error=sign-conversion" --copt="-Wno-deprecated-declarations"`
Enable C++ tests for Bazel 7 on mac PiperOrigin-RevId: 610573579 10 months ago			`common --repo_env=BAZEL_NO_APPLE_CPP_TOOLCHAIN=1`
Reduce our reliance on COPTS variable for compiler flags It's somewhat tedious to explicitly set this option on all of our C++ targets, so I think ideally we should rely primarily on bazelrc files for setting compiler flags. I tried to completely remove `COPTS`, but unfortunately that did not work out--we have so many `-Wsign-compare` warnings that I think we need to keep suppressing them for now or else we will get a lot of complaints. However, I was able to get to the point where `-Wno-sign-compare` is the only flag we need in `COPTS` for non-Windows builds. I explicitly set `-DHAVE_ZLIB` on just the two targets that need it, and removed `-Wno-nonnull` since we are already compliant with that warning. I moved `-Woverloaded-virtual` to our bazelrc files so that CI will enforce that we remain compliant with that. PiperOrigin-RevId: 684863987 2 months ago			`common --xcode_version_config=@com_google_protobuf//.github:host_xcodes`
Bump minimum C++ version to C++17 after branch cut for v29. Branch cut for v29 is done on 2024-09-30: https://github.com/protocolbuffers/protobuf/releases/tag/v29.0-rc1 The next version v30 will be a breaking release. The release date is scheduled after the EOL of C++14 support on 2024-12-15 for Google open source projects generally: https://github.com/google/oss-policies-info/blob/main/foundational-cxx-support-matrix.md This commit allows us to start taking advantage of C++17 features now. Some issues I ran into while upgrading: Two GCC 9.5 bugs related to -Wunused-but-set-parameter: - https://godbolt.org/z/qo51cKe7b - https://godbolt.org/z/65qW3vGhP Another GCC warning related to -Wself-assign in a template. There is a custom ASAN check that is not yet open sourced. I'll see if I can open source them in a subsequent commit. #test-continuous PiperOrigin-RevId: 687435042 2 months ago