Lines Matching +full:bazel +full:- +full:release

7 [here](https://github.com/google/fruit/wiki/install#building-fruit-manually).
16 [Bazel](https://www.bazel.io) (configured in `BUILD` files).
28 mkdir build-debug
29 cd build-debug
30 cmake .. -DCMAKE_BUILD_TYPE=Debug -DCMAKE_CXX_FLAGS="-Werror -DFRUIT_DEBUG=1 -DFRUIT_EXTRA_DEBUG=1 …
31 make -j 16
33 py.test-3 -n auto
39 [here](https://travis-ci.org/google/fruit/builds). The CI configuration is defined in
58 * Using CMake or Bazel
63 ([list of images](https://hub.docker.com/r/polettimarco/fruit-basesystem/tags/)).
68 export OS=linux; export COMPILER='clang-3.9'; export STL='libstdc++'; export UBUNTU='16.04'; extras…
83 This is often very useful to e.g. re-run a compilation manually with additional debug flags.
91 export NJOBS=16; export OS=linux; export COMPILER='clang-3.9'; export STL='libstdc++'; export UBUNT…
107                 "name": "x86-Debug",
111 …"cmakeCommandArgs": "-DBOOST_DIR=C:\\boost\\boost_1_62_0 -DCMAKE_BUILD_TYPE=Debug -DFRUIT_ADDITION…
112                 "buildCommandArgs": "-m -v:minimal"
115                 "name": "x86-Release",
117                 "configurationType": "Release",
119 …              "cmakeCommandArgs": "-DBOOST_DIR=C:\\boost\\boost_1_62_0 -DCMAKE_BUILD_TYPE=Release",
120                 "buildCommandArgs": "-m -v:minimal"
123                 "name": "x64-Debug",
127 …"cmakeCommandArgs": "-DBOOST_DIR=C:\\boost\\boost_1_62_0 -DCMAKE_BUILD_TYPE=Debug -DFRUIT_ADDITION…
128                 "buildCommandArgs": "-m -v:minimal"
131                 "name": "x64-Release",
133                 "configurationType": "Release",
135 …              "cmakeCommandArgs": "-DBOOST_DIR=C:\\boost\\boost_1_62_0 -DCMAKE_BUILD_TYPE=Release",
136                 "buildCommandArgs": "-m -v:minimal"
143 If you don't want to use Boost, you can replace the `-DBOOST_DIR=...` flags above with `-DFRUIT_USE…
145 … Visual Studio (from the menu: CMake -> Cache -> Generate -> CMakeLists.txt) and build Fruit (from…
147 You can also run tests, but *only* from the command-line (after building Fruit from Visual Studio),…
151 You'll also the `pytest` and `pytest-xdist` packages. You can install them with:
154     pip install pytest-xdist
160 * In Visual Studio, open the Output view (from the menu: View -> Output) and select "CMake" in the …
162 …0-4eec-6438-a358-e1253b7e86ff\build\x64-Debug`, you can run `cd "C:\Users\Marco\AppData\Local\CMak…
164 * Then run pytest, e.g. `py.test -n auto`.
172 [here](https://travis-ci.org/google/fruit) to check if that's the case).
178 * Is formatted correctly ([more details here](#code-style)) 
179 * Has appropriate tests (if your change is user-visible, or if you're introducing new branches that…
190 * Bazel ([installation instructions](https://www.bazel.io/docs/install.html))
196 This command uses Bazel to run the tests (so you need to have it installed in order to use this).
197 Bazel has a much more fine-grained picture of what tests depend on what source files, so it will of…
201 because all tests will be re-run anyway.
205 bazel test --python_path=/usr/bin/python3 \
206            --test_output=errors \ 
207            --test_summary=terse \
218 mkdir build-coverage
219 cd build-coverage
220 CXX=g++-6 cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo -DFRUIT_ENABLE_COVERAGE=ON
221 make -j 10
222 (cd tests; py.test-3 -n auto)
223 lcov --rc lcov_branch_coverage=1 --capture --directory . --output-file coverage.info
224 lcov --rc lcov_branch_coverage=1 --remove coverage.info '/usr/include/*' '/tmp/*' -o coverage-filte…
225 genhtml --no-function-coverage --rc lcov_branch_coverage=1 --rc genhtml_hi_limit=100 coverage-filte…
226 google-chrome html/index.html
241 C++ code in Fruit should be indented using clang-format (a `.clang-format` file is provided in the …
242 directory). You can re-indent all code using this command:
245 $ clang-format -i $(git ls-files | egrep '\.cpp|\.h' )