Explicitly use clang for host tools

Bug: 92
Change-Id: Ibc43b6eb0573f018b4bd32bfad85ab152726c01f
1 file changed
tree: 4ea68baeb5ba4ff7f6ce4ed439b25d5d6e41a9e5
  1. docs/
  2. pw_base64/
  3. pw_bloat/
  4. pw_boot_armv7m/
  5. pw_build/
  6. pw_checksum/
  7. pw_cli/
  8. pw_cpu_exception/
  9. pw_cpu_exception_armv7m/
  10. pw_docgen/
  11. pw_doctor/
  12. pw_dumb_io/
  13. pw_dumb_io_baremetal_stm32f429/
  14. pw_dumb_io_stdio/
  15. pw_env_setup/
  16. pw_kvs/
  17. pw_log/
  18. pw_log_basic/
  19. pw_minimal_cpp_stdlib/
  20. pw_module/
  21. pw_polyfill/
  22. pw_preprocessor/
  23. pw_presubmit/
  24. pw_protobuf/
  25. pw_protobuf_compiler/
  26. pw_span/
  27. pw_status/
  28. pw_string/
  29. pw_target_runner/
  30. pw_tokenizer/
  31. pw_toolchain/
  32. pw_unit_test/
  33. pw_varint/
  34. pw_watch/
  35. targets/
  36. .clang-format
  37. .gitignore
  38. .gn
  39. .pylintrc
  40. AUTHORS
  41. BUILD
  42. BUILD.gn
  43. BUILDCONFIG.gn
  44. CMakeLists.txt
  45. CODE_OF_CONDUCT.md
  46. CONTRIBUTING.md
  47. LICENSE
  48. modules.gni
  49. pw_vars_default.gni
  50. README.md
  51. WORKSPACE
README.md

Pigweed

Pigweed is a collection of embedded-focused libraries, called “modules”. These modules are designed for small-footprint MMU-less microcontrollers like the ST Micro STM32L452 or the Nordic NRF82832. The modules are designed to facilitate easy integration into existing codebases.

Pigweed is in the early stages of development, and should be considered experimental. We’re continuing to evolve the platform and add new modules. We value developer feedback along the way.

Pigweed is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

Getting Started

$ git clone sso://pigweed.googlesource.com/pigweed/pigweed ~/pigweed
$ cd ~/pigweed
# Only need to run auth-login once per machine.
$ pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py auth-login
$ . pw_env_setup/bootstrap.sh

You can use . pw_env_setup/setup.sh in place of . pw_env_setup/bootstrap.sh. Both should work every time, but bootstrap.sh tends to remove and reinstall things at the expense of time whereas setup.sh assumes things have already been installed and only sets environment variables.

If you‘re using Homebrew and you get an error saying module 'http.client' has no attribute 'HTTPSConnection' then your Homebrew Python was not set up to support SSL. Ensure it’s installed with brew install openssl and then run brew uninstall python && brew install python. After that things should work.

The environment setup script will pull down the versions of tools necessary to build Pigweed and add them to your environment. You can then build with GN, CMake, or Bazel. You can also confirm you're getting the right versions of tools—they should be installed under .cipd/.

Build for the host with GN

$ which gn
~/pigweed/.cipd/pigweed.ensure/gn
$ gn gen out/host
$ ninja -C out/host

Build for the host with CMake

$ which cmake
~/pigweed/.cipd/pigweed.ensure/bin/cmake
$ cmake -B out/cmake-host -S . -G Ninja
$ ninja -C out/cmake-host

Build for the host with Bazel

$ which bazel
~/pigweed/.cipd/pigweed.ensure/bazel
$ bazel test //...

Build for the STM32F429 Discovery board

$ gn gen --args='pw_target_config = "//targets/stm32f429i-disc1/target_config.gni"' out/disco
$ ninja -C out/disco
$ pw test --root out/disco/ --runner stm32f429i_disc1_unit_test_runner

The CMake and Bazel builds do not yet support building for hardware.

To flash firmware to an STM32 Discovery development board (and run pw test) from macOS, you need to install OpenOCD. Install Homebrew using the latest instructions at https://brew.sh/, then install OpenOCD with brew install openocd.

If any of this doesn't work please file a bug.