commit | 300dcea444f00c987fc1e6b40c8a3b52c984c68a | [log] [tgz] |
---|---|---|
author | Alexei Frolov <frolv@google.com> | Mon Dec 23 13:33:59 2019 -0800 |
committer | CQ Bot Account <commit-bot@chromium.org> | Thu Dec 26 18:38:24 2019 +0000 |
tree | 7223a7f2ec8c3a17556d992bea93ac7b5bc492b3 | |
parent | def1471ede561ac97e7613a6813ab5e1f7cf081e [diff] |
pw_test_server -> pw_target_runner This change renames the pw_test_server module to pw_target_runner and integrates it into the GN build using the new Go templates. The module is updated to match the GOPATH structure under its go/ directory, and its protos are moved into the module protos directory. Additionally, the simple server and client are split into two separate programs instead of combining them into one. Change-Id: I44adeca0989dc7e15cb1a169a6ce183139dde2ce
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/.cipd/pigweed.ensure/gn $ gn gen out/host $ ninja -C out/host
$ which bazel ~/pigweed/.cipd/pigweed.ensure/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.