tools: Add script to auto convert CMakeLists.txt to BUILD.bazel

This script builds an abstract syntax tree (AST) from the if/else/endif
conditions in the given CMakeLists.txt, and uses that AST to generate
a BUILD.bazel file matching the CMake content. The script works
especially well in the drivers/ directory. It significantly reduces the
maintenance burden of the BUILD.bazel files.

Note that AND, OR and NOT logic in CMake's if (CONFIG_XXX) is not
currently supported. A proper translation of AND and OR of configs will
require Skylib's selects.config_setting_group(). This can be added to
this script in future changes.

Change-Id: Idff748c70b150ad3ee5185a7c1aefcf52f6256a4
Reviewed-on: https://pigweed-review.googlesource.com/c/zephyr/zephyr-bazel/+/348772
Commit-Queue: Yicheng Li <yichengli@google.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Willow Kaplan <wkap@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
4 files changed
tree: 09183f9009f4bc5d26f49f255a755ef806854a89
  1. .vscode/
  2. arch/
  3. bazel/
  4. boards/
  5. docs/
  6. drivers/
  7. dts/
  8. examples/
  9. include/
  10. kernel/
  11. lib/
  12. modules/
  13. pw_chrono_zephyr/
  14. pw_sync_zephyr/
  15. pw_thread_zephyr/
  16. scripts/
  17. soc/
  18. subsys/
  19. tools/
  20. .bazelversion
  21. .gitignore
  22. AUTHORS
  23. BUILD.bazel
  24. cc.bzl
  25. CONTRIBUTING.md
  26. defs.bzl
  27. generate_diff.py
  28. kconfig.bzl
  29. LICENSE
  30. MODULE.bazel
  31. MODULE.bazel.lock
  32. OWNERS
  33. README.md
  34. setup.bzl
  35. WORKSPACE
README.md

Zephyr-Bazel

The way this repository works is by overlaying itself on top of Zephyr. To get started, first make sure you have Bazel‘s skylib version 1.7.1 or greater. If you don’t have it, you can use:

http_archive(
    name = "bazel_skylib",
    sha256 = "bc283cdfcd526a52c3201279cda4bc298652efa898b10b4db0837dc51652756f",
    urls = [
        "https://mirror.bazel.build/github.com/bazelbuild/bazel-skylib/releases/download/1.7.1/bazel-skylib-1.7.1.tar.gz",
        "https://github.com/bazelbuild/bazel-skylib/releases/download/1.7.1/bazel-skylib-1.7.1.tar.gz",
    ],
)

load("@bazel_skylib//:workspace.bzl", "bazel_skylib_workspace")

bazel_skylib_workspace()

Usage in WORKSPACE

To grab the zephyr-bazel repo, use a git_repository rule in your WORKSPACE, such as:

git_repository(
    name = "zephyr-bazel",
    remote = "https://pigweed.googlesource.com/zephyr/zephyr-bazel",
    branch = "main",
)

Once you have @zephyr-bazel, we can load the patch rule to generate the Zephyr diff that will augment Zephyr to include the BUILD.zephyr rules.

load("@zephyr-bazel//:setup.bzl", "create_zephyr_patch_file")

create_zephyr_patch_file(
    name = "zephyr-patch",
    filename = "patch.diff",
    # This is optional, use it to see what's going on under the hood
    debug = True,
)

We now have a diff file at @zephyr-patch//:patch.diff. We're ready to load Zephyr.

git_repository(
    name = "zephyr",
    remote = "https://github.com/zephyrproject-rtos/zephyr.git",
    branch = "main",
    patches = [
        "@zephyr-patch//:patch.diff",
    ],
)

The final step will be to load Zephyr's python dependencies:

load("@rules_python//python:pip.bzl", "pip_parse")

pip_parse(
    name = "py_deps",
    python_interpreter_target = interpreter,
    requirements_lock = "@@zephyr//:scripts/requirements-base.txt",
)

load("@py_deps//:requirements.bzl", zephyr_install_deps = "install_deps")

zephyr_install_deps()

Usage in bzlmod

To use zephyr-bazel in bzlmod, first add it as a dependency in your project's MODULE.bazel:

bazel_dep(name = "zephyr-bazel")
git_override(
    module_name = "zephyr-bazel",
    remote = "https://pigweed.googlesource.com/zephyr/zephyr-bazel",
    branch = "main",
)

Then use the zephyr_patch_file module extension to generate a patch file and a Bazel repo with the patch file applied:

zephyr_patch_file = use_extension("@zephyr-bazel//:setup.bzl", "zephyr_patch_file")
use_repo(zephyr_patch_file, "zephyr")

pip is required by the patched zephyr repo, so your project needs to inject it:

pip = use_extension("@rules_python//python/extensions:pip.bzl", "pip")
# Load the Zephyr pip requirements
pip.parse(
    hub_name = "pip",
    python_version = "3.11",
    requirements_lock = "@zephyr//:scripts/requirements-base.txt",
)
use_repo(pip, "pip")

inject_repo(zephyr_patch_file, "pip")

Application

In your main application, you can now use the Zephyr utilities for building your app.

load("@zephyr//:defs.bzl", "dts_cc_library")

dts_cc_library(
    name = "app_native_sim_dts",
    dts_lib = "@zephyr//boards/native/native_sim:native_sim",
)

cc_binary(
    ...
    deps = [
        ...
        "@zephyr//:zephyr",
    ] + select({
        "@platform//cpu:x86_64": [
            ":app_native_sim_dts",
            "@zephyr//include:posix",
        ],
    }),
    copts = select({
        "@platform//cpu:x86_64": [
            "-DCONFIG_ARCH_POSIX=1",
        ],
    }),
)

Examples

There is currently just 1 example, you can run it via:

$ cd examples/hello_dts
$ bazel run :app

Or, you can run the tests via:

$ cd examples/hello_dts
$ bazel test //...