9113c9fea2
- Remove the path filter for init_virtualenv since the build depends on Python. - Add --clean-py option for cleaning only the Python venv. - Rename --continue to --keep-going for consistency with Bazel. - Make updates to Git path handling to correctly handle absolute versus relative paths. - Make the .presubmit directory relative to the root of the repo. Change-Id: I9b2ce32dd4e1a9c993a10f37c252a685625c46ad |
||
|---|---|---|
| docs | ||
| env_setup | ||
| pw_bloat | ||
| pw_build | ||
| pw_cli | ||
| pw_docgen | ||
| pw_dumb_io | ||
| pw_dumb_io_baremetal_stm32f429 | ||
| pw_dumb_io_stdio | ||
| pw_module | ||
| pw_preprocessor | ||
| pw_presubmit/py | ||
| pw_span | ||
| pw_status | ||
| pw_string | ||
| pw_test_server | ||
| pw_toolchain | ||
| pw_unit_test | ||
| pw_varint | ||
| targets | ||
| .clang-format | ||
| .gitignore | ||
| .gn | ||
| .pylintrc | ||
| AUTHORS | ||
| BUILD | ||
| BUILD.gn | ||
| BUILDCONFIG.gn | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| modules.gni | ||
| pw_vars_default.gni | ||
| README.md | ||
| WORKSPACE | ||
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/cipd/cipd.py auth-login # Once per machine.
$ . env_setup/setup.sh
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
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 the STM32F429 Discovery board. (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
$ pw test --root out/disco/ --runner stm32f429i_disc1_unit_test_runner -- --port /dev/ttyACM0
If any of this doesn't work please file a bug.