commit | 91075ebb2367073053be359a3baa17b9fa526b70 | [log] [tgz] |
---|---|---|
author | Ted Pudlik <tpudlik@google.com> | Wed Jan 24 19:12:18 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 24 19:12:18 2024 +0000 |
tree | e91b1abb76a9c49e86a6c41c16deb954a0856439 | |
parent | 853989651ead5f5ae95f0698ca460be6e29b11b6 [diff] |
docs: How to use a single Pigweed module in Bazel Provide some guidance on how to depend on Pigweed as "just a library" from a pre-existing Bazel project. In response to an old request from Kayce (sorry, internal-only link: https://docs.google.com/document/d/1HkccKsBmC1IALJMszrLi9LBnK9mpHaiytL66txozVJU/edit?resourcekey=0-pIsK8e1pXn_CGdX-IYRyTg&disco=AAAA_QKPhdM) Change-Id: I2ecc724501741bd7f1e129c16bf23f21db8c9816 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/188922 Commit-Queue: Ted Pudlik <tpudlik@google.com> Reviewed-by: Kayce Basques <kayce@google.com>
Pigweed is an open source collection of embedded-targeted libraries–or as we like to call them, modules. These modules are building blocks and infrastructure that enable faster and more reliable development on small-footprint MMU-less 32-bit microcontrollers like the STMicroelectronics STM32L452 or the Nordic nRF52832.
For more information please see our website: https://pigweed.dev/.