... | ... | @@ -7,4 +7,24 @@ In the build directory, CMake will generate a *CMakeCache.txt* file that contain |
|
|
* **CMAKE_BUILD_TYPE**: setting this variable do **Debug** will trigger a debug build.
|
|
|
* **CMAKE_CXX_FLAGS_DEBUG**: this contains the compilation option for debug build. Some of them will have a huge (bad) impact on performance. Apart from the traditional **-g** option, one can add *when compiling with Intel* a combination of:
|
|
|
* **-D_GLIBCXX_DEBUG** with will enable a lot of runtime checks into the support library, including systematic bound checking for the C++ STL containers.
|
|
|
* **-fp-trap-all=common** with will activate floating point checking, including division by zero. Can |
|
|
\ No newline at end of file |
|
|
* **-fp-trap-all=common** with will activate floating point checking, including division by zero. Can
|
|
|
|
|
|
## Trick and Tip
|
|
|
### Licallo
|
|
|
|
|
|
Building and running the tests in one command. We assume there is already a bulid directory configured:
|
|
|
|
|
|
```
|
|
|
$ cd <blddir>
|
|
|
$ make -j && ./tools/dev/licTest.sh
|
|
|
```
|
|
|
|
|
|
**If** you are in a purelly development phase (no production run going on) you can run the following:
|
|
|
|
|
|
```
|
|
|
$scancel -u alainm && make -j && ./tools/dev/licTest.sh
|
|
|
```
|
|
|
|
|
|
it will first cancel all your job, which can be convenient if you're working in many different configurations (debug and release for example) as it free resources. But it will kill all running jobs.
|
|
|
|
|
|
|