| commit | 572ca89be219ad1fdbde72be2c47701e982cebfd | [log] [tgz] |
|---|---|---|
| author | Alexei Frolov <frolv@google.com> | Mon Dec 02 10:34:29 2019 -0800 |
| committer | Alexei Frolov <frolv@google.com> | Mon Dec 02 21:48:12 2019 +0000 |
| tree | 277c35d652e615ef597e887f7f89c2f98429cb83 | |
| parent | 3895a127c755e524440f63435038ba4e52a2f2af [diff] |
Add environment variable to pw_cli.process module This change sets an environment variable in the subprocess run by pw_cli.process.run() to indicate that it is running as a subprocess. Change-Id: I1def3259b62578a156a4b374d41af99692147699
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
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.