zephyr/defines: Move KERNEL and __ZEPHYR__ to toolchains

Moves the KERNEL and __ZEPHYR__ defines out of the zephyr_cc_library and
into the toolchain definition instead so that it's globally available.

Change-Id: Id5ebe2d3a59f02feffdcadb1165a0a318f707886
Reviewed-on: https://pigweed-review.googlesource.com/c/zephyr/zephyr-bazel/+/435155
8 files changed
tree: 45efb6e3d4f61a2b62e515336c713c6947ca52b6
  1. .vscode/
  2. bazel/
  3. bazel_overlay/
  4. build_config/
  5. designs/
  6. docs/
  7. examples/
  8. modules/
  9. pw_tests/
  10. scripts/
  11. tests/
  12. third_party/
  13. toolchain/
  14. tools/
  15. ztests/
  16. .bazelignore
  17. .bazelrc
  18. .bazelversion
  19. .gitignore
  20. AUTHORS
  21. BUILD.bazel
  22. common.bazelrc
  23. CONTRIBUTING.md
  24. generate_diff.py
  25. LICENSE
  26. MODULE.bazel
  27. MODULE.bazel.lock
  28. naming.bzl
  29. OWNERS
  30. pigweed_dep.MODULE.bazel
  31. pw
  32. README.md
  33. setup.bzl
  34. workflows.json
  35. WORKSPACE
README.md

Zephyr-Bazel

The way this repository works is by overlaying itself on top of Zephyr to provide Bazel build capability to the underlying Zephyr repository.

Getting Started

User Guide

For more information on the architecture and internal design of Zephyr-Bazel, see the design documents in the designs folder of this repository: