| commit | b627b416f48402ab508850a424ce8adf5cfd0fc5 | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@google.com> | Wed Nov 27 09:41:25 2019 -0800 |
| committer | Wyatt Hepler <hepler@google.com> | Wed Nov 27 11:18:08 2019 -0800 |
| tree | e83ae63fbd3faf49371a80874f76cb098fcadeb7 | |
| parent | 79f0d9a99b60be068b8570f9b496cd79dc150be7 [diff] |
Add .pylintrc Generated a default pylintrc with pylint's --generate-rcfile option and made a few modifications: * Set jobs to 0 (sets to number of cores). * Disable fixme and subprocess-run-check. * Always expect LF. * Adjust min/max counts to avoid warnings. Change-Id: I0a57457e39cce9191172aaa1dc694d5fb4474f0b
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/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.