| commit | 30b42ef7a16d1dee17c9a71f90854e1be20c161f | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Wed Nov 27 08:54:06 2019 -0800 |
| committer | Rob Mohr <mohrr@google.com> | Wed Nov 27 21:24:49 2019 +0000 |
| tree | b3aab3f0945f603b3cf5df75d1763618dd5dadcb | |
| parent | 8253ad8d66a074a5464601a7290ccee874a499f5 [diff] |
Bazel build fixes. Clang-tidy complains about operator=() not returning *this, even though that's what it was doing anyway. Then add a direct dependency, add a header to a library, and sync up argument names in a method declaration with the definition. Change-Id: Ib64f050ae74309640a4ae1346e617a932377f63e
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.