Change Python3 CIPD package.

Change-Id: I95ccb70708a1028141239033183862d402461879
1 file changed
tree: b66f7050dee50ae0c8118c2126d26f6f71e63437
  1. docs/
  2. env_setup/
  3. pw_bloat/
  4. pw_build/
  5. pw_cli/
  6. pw_docgen/
  7. pw_dumb_io/
  8. pw_dumb_io_baremetal_stm32f429/
  9. pw_dumb_io_stdio/
  10. pw_preprocessor/
  11. pw_presubmit/
  12. pw_span/
  13. pw_status/
  14. pw_string/
  15. pw_toolchain/
  16. pw_unit_test/
  17. targets/
  18. .clang-format
  19. .gitignore
  20. .gn
  21. AUTHORS
  22. BUILD
  23. BUILD.gn
  24. BUILDCONFIG.gn
  25. CONTRIBUTING.md
  26. LICENSE
  27. modules.gni
  28. presubmit.py
  29. pw_vars_default.gni
  30. README.md
  31. WORKSPACE
README.md

Pigweed Embedded Oriented Software Libraries

Pigweed is a collection of embedded-focused libraries, which we call "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.

Getting Started

$ git clone sso://pigweed.googlesource.com/pigweed/pigweed ~/pigweed
$ cd ~/pigweed
$ . env_setup/setup.sh

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 either GN or Bazel. You can also confirm you're getting the right versions of tools—they should be installed under env_setup/.

$ which gn
~/pigweed/env_setup/cipd/tools/gn
$ gn gen out/host
$ ninja -C out/host
$ which bazel
~/pigweed/env_setup/cipd/tools/bazel
$ bazel test //...

And do the following to test on hardware. (The bazel build does not yet support building for hardware.)

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

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