## Curve 编译 Curve bazel 编译分享 程义 - 存储计算部 2022年11月11日 ## 更新内容 1 升级 bazel 到 4.2.2 2 支持 Debian9、Debian10、Debian11 3 支持 gcc clang ## 1 ## 编译 Debian11-Dockerfile .bazelrc bazel 版本：4.2.2 ( bazelisk) cd /curve/ # 使用 gcc 编译 bazel build -config=gcc7-later ... # use '-faligned-new' to enable C++17 over-aligned new support # 使用 clang 编译 CC=clang CXX=clang++ bazel build ... ## 2 ## 制作镜像 docker run -v $(pwd):/curve -v /root/.cache/bazel:/root/.cache/bazel -it opencurvedocker/curve-base:build-debian11 # 容器内 cd /curve/curvefs make build os=debian11 # 容器外 # curvefs sudo make image

## GopherChina2018 ## 流利说 ## Bazel build //:Go  ## 流利说 ## Help everyone become a global citizen! github/lingochamp ## ## Agenda • Package Management • Code Management (Multi languages) • Bazel build //:Go • Demo • Q & A Let's talk about ## Package Management ## vendor Go 1.5 introduced experimental support option 声明导致没法编译 ## How to share knowledge? ## I ntroducing ☐ Bazel ## Open source version of Blaze Google’s indoor build system https://bazel.build ### Blaze ca. 2017 • 2B LOC in monorepo • 45K commits/day

流利说 Bazel build //:Go yuan@liulishuo.com ’ alt=‘OCR图片’/> 流利说 Help everyone become a global citizen! github/lingochamp 何源 yuan@liulishuo.com 2014年底加入流利说，目前主要负责Platform Team 来流利说之前在 ThePlant 杭州工作 杭州工作 Agenda Package Management Code Management (Multi languages) Bazel build //:Go Demo Q&A Let’s talk about Package Management vendor Go 1.5 introduced experimental support for a “vendor” go_package option 声明导致没法编译 How to share knowledge? Introducing Bazel Open source version of Blaze Google’s indoor build system https://bazel.build Blaze ca. 2017 2B LOC in monorepo 45K commits/day

CMake ..... 167 6.2 CLion ..... 168 6.3 Visual Studio ..... 174 6.4 Autotools ..... 179 6.5 Bazel ..... 180 6.6 Makefile ..... 180 6.7 Xcode ..... 181 6.8 Meson ..... 181 6.9 Android .... Getting started with Autotools • Getting started with Meson • Getting started with Bazel • Getting started with Bazel 7.x #### 4.1.2 Using build tools as Conan packages In the previous example, we built projects using Bazel. They can be imported from conan.tools.google. The most relevant tools are: - BazelDeps: the dependencies generator for Bazel, which generates a [DEPENDENCY]/BUILD.bazel file for each

CMake ..... 167 6.2 CLion ..... 168 6.3 Visual Studio ..... 174 6.4 Autotools ..... 179 6.5 Bazel ..... 180 6.6 Makefile ..... 180 6.7 Xcode ..... 181 6.8 Meson ..... 181 6.9 Android .... Getting started with Autotools • Getting started with Meson • Getting started with Bazel • Getting started with Bazel 7.x #### 4.1.2 Using build tools as Conan packages In the previous example, we built projects using Bazel. They can be imported from conan.tools.google. The most relevant tools are: - BazelDeps: the dependencies generator for Bazel, which generates a [DEPENDENCY]/BUILD.bazel file for each

CMake ..... 169 6.2 CLion ..... 170 6.3 Visual Studio ..... 176 6.4 Autotools ..... 181 6.5 Bazel ..... 182 6.6 Makefile ..... 182 6.7 Xcode ..... 183 6.8 Meson ..... 183 6.9 Android .... Getting started with Autotools • Getting started with Meson • Getting started with Bazel • Getting started with Bazel 7.x #### 4.1.2 Using build tools as Conan packages In the previous example, we built projects using Bazel. They can be imported from conan.tools.google. The most relevant tools are: - BazelDeps: the dependencies generator for Bazel, which generates a [DEPENDENCY]/BUILD.bazel file for each

CMake ..... 169 6.2 CLion ..... 170 6.3 Visual Studio ..... 176 6.4 Autotools ..... 181 6.5 Bazel ..... 182 6.6 Makefile ..... 182 6.7 Xcode ..... 183 6.8 Meson ..... 183 6.9 Premake .... Getting started with Autotools • Getting started with Meson • Getting started with Bazel • Getting started with Bazel 7.x #### 4.1.2 Using build tools as Conan packages In the previous example, we built projects using Bazel. They can be imported from conan.tools.google. The most relevant tools are: - BazelDeps: the dependencies generator for Bazel, which generates a [DEPENDENCY]/BUILD.bazel file for each

CMake ..... 167 6.2 CLion ..... 168 6.3 Visual Studio ..... 174 6.4 Autotools ..... 179 6.5 Bazel ..... 180 6.6 Makefile ..... 180 6.7 Xcode ..... 181 6.8 Meson ..... 181 6.9 Android .... Getting started with Autotools • Getting started with Meson • Getting started with Bazel • Getting started with Bazel 7.x #### 4.1.2 Using build tools as Conan packages In the previous example, we built projects using Bazel. They can be imported from conan.tools.google. The most relevant tools are: - BazelDeps: the dependencies generator for Bazel, which generates a [DEPENDENCY]/BUILD.bazel file for each

Integrations 167 6.1 CMake 167 6.2 CLion 168 6.3 Visual Studio 174 6.4 Autotools 179 6.5 Bazel 180 6.6 Makefile 180 6.7 Xcode 181 6.8 Meson 181 6.9 Android 182 6.10 JFrog 182 7 Examples Getting started with Autotools • Getting started with Meson • Getting started with Bazel • Getting started with Bazel 7.x #### 4.1.2 Using build tools as Conan packages In the previous example, we built projects using Bazel. They can be imported from conan.tools.google. The most relevant tools are: - BazelDeps: the dependencies generator for Bazel, which generates a [DEPENDENCY]/BUILD.bazel file for each

Integrations 167 6.1 CMake 167 6.2 CLion 168 6.3 Visual Studio 174 6.4 Autotools 179 6.5 Bazel 180 6.6 Makefile 180 6.7 Xcode 181 6.8 Meson 181 6.9 Android 182 6.10 JFrog 182 7 Examples Getting started with Autotools • Getting started with Meson • Getting started with Bazel • Getting started with Bazel 7.x #### 4.1.2 Using build tools as Conan packages In the previous example, we built projects using Bazel. They can be imported from conan.tools.google. The most relevant tools are: - BazelDeps: the dependencies generator for Bazel, which generates a [DEPENDENCY]/BUILD.bazel file for each