| commit | e94839312b20cadee084ad9f9f8ea092935fdd84 | [log] [tgz] |
|---|---|---|
| author | Keir Mierle <keir@google.com> | Mon Dec 23 12:32:42 2019 -0800 |
| committer | Keir Mierle <keir@google.com> | Mon Dec 23 12:46:45 2019 -0800 |
| tree | 93434d8bee331067f4fe08fa99b1060f2fad71a4 | |
| parent | fa2fbe609d57dee37ac52831411db93dd3080ca1 [diff] |
pw_watch: Clear screen and add build banner This makes the watcher clear the terminal before starting a build, to make it clearer what terminal output is associated with the current build. Additionally, a "BUILD" banner is now printed at the top to indicate that a build is starting. The approach of clearing the screen is also what various file watchers from the JavaScript world do. Example output: ██████╗ ██╗ ██╗██╗██╗ ██████╗ ██╔══██╗██║ ██║██║██║ ██╔══██╗ ██████╔╝██║ ██║██║██║ ██║ ██║ ██╔══██╗██║ ██║██║██║ ██║ ██║ ██████╔╝╚██████╔╝██║███████╗██████╔╝ ╚═════╝ ╚═════╝ ╚═╝╚══════╝╚═════╝ 20191223 12:41:11 INF Change detected: ./pw_varint/varint_test.cc 20191223 12:41:11 INF Starting build with 2 directories 20191223 12:41:11 INF [1/2] Starting build: out/disco ninja: Entering directory `out/disco' ninja: no work to do. 20191223 12:41:11 INF [1/2] Finished build: out/disco (OK) 20191223 12:41:11 INF [2/2] Starting build: out/host ninja: Entering directory `out/host' ninja: no work to do. 20191223 12:41:11 INF [2/2] Finished build: out/host (OK) 20191223 12:41:11 INF Finished; all successful. .------------------------------------ | | OK out/disco | OK out/host | '------------------------------------ ██████╗ █████╗ ███████╗███████╗██╗ ██╔══██╗██╔══██╗██╔════╝██╔════╝██║ ██████╔╝███████║███████╗███████╗██║ ██╔═══╝ ██╔══██║╚════██║╚════██║╚═╝ ██║ ██║ ██║███████║███████║██╗ ╚═╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ Bug: 39 Change-Id: I4383ff489aa3d51b8320fa514001e95529b8db85
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.