... | ... | @@ -8,16 +8,26 @@ in different ways if you are compiling the unit tests or you are compiling exter |
|
|
* defining the macro SE_CLASS1 before include any openfpm headers enable security enhancements of class1,
|
|
|
* define the macro SE_CLASS2 before include any openfpm headers enable security enhancements of class2
|
|
|
* define the macro SE_CLASS3 before include any openfpm headers enable security enhancements of class3
|
|
|
* define the macro
|
|
|
|
|
|
additionally the are are macro that define what to do in case of error
|
|
|
|
|
|
* STOP_ON_ERROR terminate the program before doing something that can produce a crash of the program
|
|
|
* THROW_ON_ERROR it throw an error, that can be catched and the user can recover from this error or do other operations
|
|
|
|
|
|
By default the program report the error but continue the execution
|
|
|
|
|
|
for more information visit [here](http://ppmcore.mpi-cbg.de:4567/security-enhancements)
|
|
|
|
|
|
### Unit test
|
|
|
|
|
|
OpenFPM is in general is only header library with few exceptions, to compile the unit tests there are 4 that can be considered the most important options, in the install script these option are passed with -c "--enable-se-class1 --enable-se-class2 --enable-se-class3 --enable-debug"
|
|
|
In case of compilation the following options are available
|
|
|
|
|
|
* --enable-debug this option disable the optimizer and include debug information in the executables
|
|
|
* --enable-se-class1
|
|
|
*
|
|
|
*
|
|
|
* --with-action-on-error |
|
|
--enable-se-class1 --enable-se-class2 --enable-se-class3 --enable-debug"
|
|
|
|
|
|
* --enable-se-class1 same as SE_CLASS1
|
|
|
* --enable-se-class2 same as SE_CLASS2
|
|
|
* --enable-se-class3 same as SE_CLASS3
|
|
|
* --with-action-on-error=throw same as THROW_ON_ERROR
|
|
|
* --with-action-on-error=error same as STOP_ON_ERROR
|
|
|
|
|
|
for more information visit [here](http://ppmcore.mpi-cbg.de:4567/security-enhancements) |