commit | 43158d0077eb52f81a092556937d4535c6d1e508 | [log] [tgz] |
---|---|---|
author | Wyatt Hepler <hepler@google.com> | Fri Dec 13 11:06:36 2019 -0800 |
committer | CQ Bot Account <commit-bot@chromium.org> | Fri Dec 13 21:53:57 2019 +0000 |
tree | 1945bc7cf0ae577251f92fb3d97eaf6f77f93b35 | |
parent | 9e0145df67855f05942ac98655269eb4ec31c976 [diff] |
pw_presubmit: Fix running from different directory Replace --repository with -C, which changes the directory before doing anything. Change-Id: I630ebb198122320aa402277f365dec9e44b696c6
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.
$ 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.