Skip to content

Build Bazel with C++17.#20085

Closed
tjgq wants to merge 1 commit intobazelbuild:masterfrom
tjgq:c++17
Closed

Build Bazel with C++17.#20085
tjgq wants to merge 1 commit intobazelbuild:masterfrom
tjgq:c++17

Conversation

@tjgq
Copy link
Copy Markdown
Contributor

@tjgq tjgq commented Nov 7, 2023

In upcoming changes, we'd like to have the ability to use C++17 features.
This ensures that such code will build successfully on the various CI
platforms, regardless of the C++ standard version the compiler defaults to.

In upcoming changes, we'd like to have the ability to use C++17 features.
This ensures that such code will build successfully on the various CI
platforms, regardless of the C++ standard version the compiler defaults to.
@tjgq tjgq marked this pull request as ready for review November 13, 2023 12:25
@tjgq tjgq requested a review from coeuvre November 13, 2023 13:32
Copy link
Copy Markdown
Member

@coeuvre coeuvre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

cc @meteorcloudy

@meteorcloudy
Copy link
Copy Markdown
Member

Should we backport this to 7.0.0?

@tjgq
Copy link
Copy Markdown
Contributor Author

tjgq commented Nov 13, 2023

@bazel-io fork 7.0.0

I see no downside to backporting.

@tjgq tjgq added the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Nov 13, 2023
@coeuvre
Copy link
Copy Markdown
Member

coeuvre commented Nov 13, 2023

Yeah, we need to backport to 7.0.0 if we want to include output service server code in 7.x later.

@keertk
Copy link
Copy Markdown
Member

keertk commented Nov 13, 2023

@bazel-io fork 7.0.0

@keertk keertk added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Nov 13, 2023
@github-actions github-actions Bot removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Nov 13, 2023
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request Nov 13, 2023
In upcoming changes, we'd like to have the ability to use C++17 features.
This ensures that such code will build successfully on the various CI
platforms, regardless of the C++ standard version the compiler defaults to.

Closes bazelbuild#20085.

PiperOrigin-RevId: 581952933
Change-Id: I0753249e2182b3ab499bc91a384ad93ec59d65f8
keertk pushed a commit that referenced this pull request Nov 13, 2023
In upcoming changes, we'd like to have the ability to use C++17
features.
This ensures that such code will build successfully on the various CI
platforms, regardless of the C++ standard version the compiler defaults
to.

Closes #20085.

Commit
ba38aa2

PiperOrigin-RevId: 581952933
Change-Id: I0753249e2182b3ab499bc91a384ad93ec59d65f8

Co-authored-by: Tiago Quelhas <tjgq@google.com>
@iancha1992
Copy link
Copy Markdown
Member

The changes in this PR have been included in Bazel 7.0.0 RC5. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc.
Thanks!

@tjgq tjgq deleted the c++17 branch March 7, 2024 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants