| commit | 5b6fa2aa0565c01f619d66a7b251312ce42b890c | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@google.com> | Mon Nov 25 09:58:25 2019 -0800 |
| committer | Wyatt Hepler <hepler@google.com> | Wed Nov 27 22:34:02 2019 +0000 |
| tree | 8d62963b59babe4365c4f6789b9828900b4ee4d6 | |
| parent | 13225146e97f6c8c825f104894741f02bd26a84d [diff] |
presubmit.py: Add several new presubmit checks - Add presubmit checks for: * clang/gcc/arm GN builds * clang-format * clang-tidy * yapf * mypy * copyright header Many of these checks are not yet passing on the whole repo. - Define --clean option for deleting cached .presubmiit files. - Define --skip_init option for whether to skip the init step. Change-Id: I223964c9fe076bfb8c882f4a358e3f8c6de6806b
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.