protobuf/examples/.bazelrc

common --enable_platform_specific_config

# Needed for java_lite_proto_library, that's using ProguardSpecProvider
# TODO: Once the provider is ported to Starlark the flag may be removed.
common --experimental_google_legacy_api

build:linux --cxxopt=-std=c++14 --host_cxxopt=-std=c++14
build:macos --cxxopt=-std=c++14 --host_cxxopt=-std=c++14

common:windows --enable_runfiles

build --experimental_remote_cache_eviction_retries=5
build --remote_download_outputs=all
Migrate bazel tests to protobuf-ci. This will allow them to reuse our bazelrc and remote caching setup. This also silences the non-bzlmod windows test that's hitting the windows path length. PiperOrigin-RevId: 626390416 8 months ago			`common --enable_platform_specific_config`

Move java_{lite_}proto_library from Bazel repository Tests will be submitted in separate PRs. PiperOrigin-RevId: 674321127 3 months ago			`# Needed for java_lite_proto_library, that's using ProguardSpecProvider`
			`# TODO: Once the provider is ported to Starlark the flag may be removed.`
			`common --experimental_google_legacy_api`

Migrate bazel tests to protobuf-ci. This will allow them to reuse our bazelrc and remote caching setup. This also silences the non-bzlmod windows test that's hitting the windows path length. PiperOrigin-RevId: 626390416 8 months ago			`build:linux --cxxopt=-std=c++14 --host_cxxopt=-std=c++14`
			`build:macos --cxxopt=-std=c++14 --host_cxxopt=-std=c++14`

			`common:windows --enable_runfiles`

			`build --experimental_remote_cache_eviction_retries=5`
			`build --remote_download_outputs=all`