envoyproxy/envoy

Switch to upstream llvm bazel config

Open

#17,660 opened on Aug 10, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/buildhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Recently bazel support landed upstream in the llvm repo here: https://github.com/llvm/llvm-project/tree/main/utils/bazel

This support is technically best effort, but I think that's not significantly different from using rules_foreign_cc to include it today. I think switching to this would improve the build experience on envoy's side, and improve the stability of those upstream configs for the community.

Contributor guide

Research direction
Understand the current LLVM integration via rules foreign cc and compare with the upstream Bazel config. Plan the migration steps and test the build.
Tech stack
cpp
Domain
backendbuild system
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Bazel
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50