From 32ddadea1713a60564ce65ccdc035e7c939b2cc1 Mon Sep 17 00:00:00 2001 From: Tim Quatmann Date: Thu, 17 Jun 2021 11:37:10 +0200 Subject: [PATCH] Added explanations on how to update gtest in the future. --- doc/update_resources.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/doc/update_resources.md b/doc/update_resources.md index e1b85e8c1..2c5f10dbe 100644 --- a/doc/update_resources.md +++ b/doc/update_resources.md @@ -13,4 +13,16 @@ In case a new patch needs to be created follow these steps: 2. Checkout a new branch 3. Apply the old patch via `git apply $STORM_DIR/resources/3rdparty/patches/eigen.patch` 4. Resolve issues, make changes, and commit them -5. Create a new patch file via `git format-patch --stdout > eigen.patch`, where `` is the tag, branch or commit from step 1 \ No newline at end of file +5. Create a new patch file via `git format-patch --stdout > eigen.patch`, where `` is the tag, branch or commit from step 1 + +## googletest / gtest + +To update gtest, simply download the new sources from [here](https://github.com/google/googletest/releases) and put them to `$STORM_DIR/resources/3rdparty/googletest`. + +The currently shipped version can be shown using + +```console +grep GOOGLETEST_VERSION $STORM_DIR/resources/3rdparty/googletest/CMakeLists.txt +``` + +We add some extra code to gtest located in `$STORM_DIR/src/test/storm_gtest.h`. Note that our code might not be compatible with future versions of gtest.