kconfig: Fix kconfig type determination

Board specific Kconfigs must be parsed manually.
Previously we just assumed they were bool types,
but for more complex builds this is not enough.
This adds more complete Kconfig parsing to read
the type for these configs.

Change-Id: I61d086752c06abb9ea1edcd6851495e954234542
Reviewed-on: https://pigweed-review.googlesource.com/c/zephyr/zephyr-bazel/+/405573
1 file changed
tree: ee9b154dab56a6c18f3b57e20906135d1a5cc6f3
  1. .vscode/
  2. bazel/
  3. bazel_overlay/
  4. build_config/
  5. docs/
  6. examples/
  7. modules/
  8. pw_tests/
  9. scripts/
  10. tests/
  11. third_party/
  12. toolchain/
  13. tools/
  14. .bazelignore
  15. .bazelversion
  16. .gitignore
  17. AUTHORS
  18. BUILD.bazel
  19. common.bazelrc
  20. CONTRIBUTING.md
  21. generate_diff.py
  22. LICENSE
  23. MODULE.bazel
  24. MODULE.bazel.lock
  25. naming.bzl
  26. OWNERS
  27. pigweed_dep.MODULE.bazel
  28. pw
  29. README.md
  30. setup.bzl
  31. 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 design of Zephyr bazel see the other design docs in the docs folder of this repository.