| commit | a6d5cc6fe4dceb698e61cf5c0500d275f1a97434 | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@google.com> | Fri Jan 17 14:15:40 2020 -0800 |
| committer | Wyatt Hepler <hepler@google.com> | Fri Jan 17 15:04:43 2020 -0800 |
| tree | e46817bc43df4509f1b36b802aa04063f68e76dc | |
| parent | 588907ad4251027d87c00f827a2a522b0945e361 [diff] |
pw_tokenizer: Make C++11 compatible - Add pw_polyfill adapters for static_assert and std::is_null_pointer. - In tokenizer, use alternative API where necessary to adapt to C++11. - Add tests that compile all of tokenize.cc and its dependencies with older C++ standards. Change-Id: I3ef81ee4d0e95fc725843c4f20906825baf77cf7
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/wrapper.py auth-login # Once per machine. $ . env_setup/bootstrap.sh
You can use . env_setup/env_setup.sh in place of . env_setup/bootstrap.sh. Both should work every time, but bootstrap.sh tends to remove and reinstall things at the expense of time whereas env_setup.sh tends to do basic checks to see if time can be saved by skipping expensive operations.
If you're using Homebrew and you get an error saying module 'http.client' has no attribute 'HTTPSConnection' then your Homebrew Python was not set up to support SSL. Ensure it's installed with brew install openssl and then run brew uninstall python && brew install python. After that things should work.
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 GN, CMake, or Bazel. You can also confirm you're getting the right versions of tools—they should be installed under .cipd/.
Build for the host with GN
$ which gn ~/pigweed/.cipd/pigweed.ensure/gn $ gn gen out/host $ ninja -C out/host
Build for the host with CMake
$ which cmake ~/pigweed/.cipd/pigweed.ensure/bin/cmake $ cmake -B out/cmake-host -S . -G Ninja $ ninja -C out/cmake-host
Build for the host with Bazel
$ which bazel ~/pigweed/.cipd/pigweed.ensure/bazel $ bazel test //...
Build for the STM32F429 Discovery board
$ gn gen --args='pw_target_config = "//targets/stm32f429i-disc1/target_config.gni"' out/disco $ ninja -C out/disco $ pw test --root out/disco/ --runner stm32f429i_disc1_unit_test_runner
The CMake and Bazel builds do not yet support building for hardware.
To flash firmware to an STM32 Discovery development board (and run pw test) from macOS, you need to install OpenOCD. Install Homebrew using the latest instructions at https://brew.sh/, then install OpenOCD with brew install openocd.
If any of this doesn't work please file a bug.