Lines Matching +full:windows +full:- +full:docker +full:- +full:msvc

7 [here](https://github.com/google/fruit/wiki/install#building-fruit-manually).
28 mkdir build-debug
29 cd build-debug
30 cmake .. -DCMAKE_BUILD_TYPE=Debug -DFRUIT_ENABLE_CLANG_TIDY=TRUE -DCMAKE_CXX_FLAGS="-Werror -DFRUIT…
31 make -j 16
33 py.test-3 -n auto
44 * In Linux, OS X and Windows
46 * Using GCC, Clang, Apple-Clang or MSVC
52 Linux tests run in Docker, using a set of images built for this purpose 
53 ([list of images](https://hub.docker.com/r/polettimarco/fruit-basesystem/tags/)).
58 export OS=linux; export COMPILER='clang-3.9'; export STL='libstdc++'; export UBUNTU='16.04'; extras…
62 `postsubmit.sh` script will run the tests under Docker to ensure repeatability of the results.
65 a Docker image containing that old Ubuntu/GCC and then run the tests inside a VM started from that …
70 docker attach fruit
73 This is often very useful to e.g. re-run a compilation manually with additional debug flags.
81 export NJOBS=16; export OS=linux; export COMPILER='clang-3.9'; export STL='libstdc++'; export UBUNT…
84 ### How to run Fruit tests on Windows
95               "name": "x64-Debug",
99 …"cmakeCommandArgs": "-DBoost_INCLUDE_DIR=C:\\boost\\boost_1_62_0  -DCMAKE_BUILD_TYPE=Debug -DFRUIT…
100               "buildCommandArgs": "-m -v:minimal",
101               "intelliSenseMode": "windows-msvc-x64"
104               "name": "x64-Debug-noboost",
108 …"cmakeCommandArgs": "-DFRUIT_USES_BOOST=False -DCMAKE_BUILD_TYPE=Debug -DFRUIT_ADDITIONAL_CXX_FLAG…
109               "buildCommandArgs": "-m -v:minimal",
110               "intelliSenseMode": "windows-msvc-x64"
118 If you don't want to use Boost, you can replace the `-DBoost_INCLUDE_DIR=...` flags above with `-DF…
120 … Visual Studio (from the menu: CMake -> Cache -> Generate -> CMakeLists.txt) and build Fruit (from…
122 You can also run tests, but *only* from the command-line (after building Fruit from Visual Studio),…
128     pip install absl-py
130     pip install pytest-xdist
136 * In Visual Studio, open the Output view (from the menu: View -> Output) and select "CMake" in the …
138 …0-4eec-6438-a358-e1253b7e86ff\build\x64-Debug`, you can run `cd "C:\Users\Marco\AppData\Local\CMak…
140 * Then run pytest, e.g. `py.test -n auto`.
148 [here](https://travis-ci.org/google/fruit) to check if that's the case).
154 * Is formatted correctly ([more details here](#code-style)) 
155 * Has appropriate tests (if your change is user-visible, or if you're introducing new branches that…
168 * Docker
173 Bazel has a much more fine-grained picture of what tests depend on what source files, so it will of…
177 because all tests will be re-run anyway.
181 bazel test --test_output=errors \ 
182            --test_summary=terse \
193 mkdir build-coverage
194 cd build-coverage
195 CXX=g++-6 cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo -DFRUIT_ENABLE_COVERAGE=ON
196 make -j 10
197 (cd tests; py.test-3 -n auto)
198 lcov --rc lcov_branch_coverage=1 --capture --directory . --output-file coverage.info
199 lcov --rc lcov_branch_coverage=1 --remove coverage.info '/usr/include/*' '/tmp/*' -o coverage-filte…
200 genhtml --no-function-coverage --rc lcov_branch_coverage=1 --rc genhtml_hi_limit=100 coverage-filte…
201 google-chrome html/index.html
216 C++ code in Fruit should be indented using clang-format (a `.clang-format` file is provided in the …
217 directory). You can re-indent all code using this command:
220 $ clang-format -i $(git ls-files | egrep '\.cpp|\.h' )