| commit | dac350b8e1b21a42827b6821d0292b2e2d6d1821 | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@google.com> | Tue Nov 26 23:11:50 2019 -0800 |
| committer | Wyatt Hepler <hepler@google.com> | Mon Dec 02 21:37:19 2019 +0000 |
| tree | 759c02791951238ab8f21b56cf12ec60c14fc997 | |
| parent | 89f02d77cd8570526131648f5b25192b640db18f [diff] |
presubmit: Improve venv setup; expand checks - Use env_setup/virtualenv/init.py to setup the Python venv. - Improve diff colorization. - Add function for finding Python packages from .py file changes. - Add check that runs Python tests. - Enable full pylint and yapf as warnings. - Delete unused code in watch.py that used an undefined variable. - Enable required python -E check. Change-Id: I5ba9882ea9ec93f006260d5636031dd0b5005a85
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.