renovate/configure
main
master
f/handleHelp-varargs
wip/refactor-focus
f/clang-format-14
hardware/ploopy
examples/factory-firmware
f/driver/keyboardiohid
tmp/zagdul
jesse/space-cadet
jesse/wip/gd32-win
macros/rearchitecture
wip/rcm-stm32
f/keyboardio-model-100
charshift/configuration
pointing-device
f/samd-testbed
f/automatic-build-nightly
f/driver/keyboardiohid-orig
f/keymap-cache-redesign
tmp/parallel-cli
tmp/arduino-cli-pre-rebase
pr_host_keymap
f/testing-event-queue
testing
epan/testing/main
epan/testing/issue-840
epan/testing/readable
epan/build/justlib
epan/build/cmake
epan/testing/hello-simulator
device/normcore
atreus2/example-layout
v1.99.6
keyboardio-m100-MP-1
keyboardio-m100-DVT-3
keyboardio-m100-DVT-2
v1.99.5
v1.99.4
v1.99.3
v1.99.2
v1.99.1
v1.99.0
v1.98.0
v1.97.0
v1.94.0
v1.93.0
v1.92.0
v1.91.0
driver/bootloader-pre-rebase
shipped-model00-xmas
work-tip
${ noResults }
1 Commits (5356514a229564c53ee81f9b6a2c04529eed88fa)
Author | SHA1 | Message | Date |
---|---|---|---|
Eric Paniagua | b1957f33e3 |
Trick arduino-builder into linking against googletest.
- Caveat: This won't work out of the box until virtual/platform.txt is updated in the bundle repo to force the appropriate include and linker paths. - arduino-builder fails if it can't find a library for any included header. fake-gtest is a library designed to fake out this detection mechanism. - Add a gtest test that exercises the simulator. This is hello-simulator_test.h. It has to be a .h or else arduino-builder will fail to compile it with one excuse or another. - Add run-simulator-googletest "target" to the build system. It will take care of running cmake and building googletest and googlemock. Of course, this requires that cmake be installed on your system. Signed-off-by: Eric Paniagua <epaniagua@google.com> |
4 years ago |