Skip to content

Re-enable Kythe xRefs publishing #2390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 8, 2025

Conversation

ivan444
Copy link
Collaborator

@ivan444 ivan444 commented Apr 11, 2025

Bump the Kythe version for the CI. Enable the xRefs action and use newer Ubuntu

Copy link

linux-foundation-easycla bot commented Apr 11, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

# Bazel renamed @com_google_protobuf to @protobuf while Kythe is still
# using it in their BUILD targets. Manually rename until the fixed Kythe is
# released.
sed -i 's/@com_google_protobuf/@protobuf/' "kythe-${KYTHE_VERSION}/BUILD"
Copy link
Collaborator

Choose a reason for hiding this comment

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

there is also repo-mapping, maybe it can work with that ? https://bazel.build/rules/lib/repo/http#http_archive-repo_mapping

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I thought of that. We used it in past. But verible is now using the Bazel modules & I don't see a way how to do remapping with the modules.

@hzeller
Copy link
Collaborator

hzeller commented Apr 24, 2025

the problem with clang-tidy is because I don't deal with the forwarding of options yet in .bazelrc, thus the -xc++ flag is not properly seen. Let me see what I can do.

@@ -25,9 +30,6 @@ common:macos --features=-supports_dynamic_linker --linkopt=-framework --linkopt=
# Since we use designated initializers (C99 ... but >= c++20), compiler really wants the c++20 mode
common:windows --compiler=clang-cl --cxxopt=/std:c++20 --host_cxxopt=/std:c++20 --client_env=BAZEL_CXXOPTS=/std:c++20

build --cxxopt="-Wno-unknown-warning-option" --host_cxxopt="-Wno-unknown-warning-option"
# TODO: this looks like benign where it happens but to be explored further
build --cxxopt="-Wno-dangling-reference" --host_cxxopt="-Wno-dangling-reference"
# Newer bisons create an unused label.
build --cxxopt="-Wno-unused-label" --host_cxxopt="-Wno-unused-label"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Looking at the current windows CI, this -Wno-unused-label also needs to go into our unix-specific config.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yep. Added the remaining ones. The windows build is still failing, but on different issues.

@hzeller
Copy link
Collaborator

hzeller commented Apr 26, 2025

Hopefully with merging head, the clang-tidy issues should disappear (#2397)

@hzeller
Copy link
Collaborator

hzeller commented May 2, 2025

I am fixing the smoke tests separately.

@hzeller
Copy link
Collaborator

hzeller commented May 2, 2025

Smoke tests fixed in #2399

@ivan444 ivan444 force-pushed the reenable_xrefs2 branch from c25853a to 6bdd3ff Compare May 5, 2025 19:27
@ivan444 ivan444 force-pushed the reenable_xrefs2 branch from 8f60453 to e2cb246 Compare May 8, 2025 11:30
@hzeller hzeller merged commit 905e34c into chipsalliance:master May 8, 2025
32 of 33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants